Flyto2 Core: arbitrary file write via unguarded data.*/file.* modules escapes sandbox to RCE (CVE-2026-77312)
Severity: critical · Patch status: patched · Since 2026-11-20 · CVE-2026-55786, CVE-2026-67429, CVE-2026-77312
Flyto2 Core (PyPI flyto-core) <= 2.26.7 is vulnerable to arbitrary file write (CVE-2026-77312, GHSA-p34x-fmph-9fjx), an incomplete fix of the earlier Critical GHSA-2956-977x-2w3r patched in v2.26.6. The earlier fix added per-module validatepathwithenvconfig() calls to a hand-picked module list, but the data. and file. write families (data.csv.write, data.jsontocsv, file.copy, file.move, and others) were omitted and still write client-controlled paths with no sandbox confinement; data.csv.write's only check is a '..' substring denylist that misses absolute paths. Any client able to run a module via the recipe engine or MCP server (unauthenticated on the HTTP MCP surface) can write attacker-controlled content to any absolute path, escaping FLYTOSANDBOXDIR, enabling overwrite of app code, recipes, ~/.bashrc, cron, or authorizedkeys and thus RCE and full host compromise. A public benign PoC demonstrates writes outside the sandbox. Fixed in flyto-core 2.26.8.
What to do
- Upgrade flyto-core to 2.26.8 immediately
- If upgrade is not possible, restrict access to the MCP server / recipe engine execute_module surface (authenticate and network-isolate it)
- Audit hosts running flyto-core for unexpected writes outside FLYTO_SANDBOX_DIR and for tampering with app code, .flyto recipes, shell rc files, cron, or authorized_keys
- Assume compromise of any host where untrusted clients could invoke modules, given RCE impact
- Rotate credentials/keys present on affected hosts
Fixed versions
Sources
All live incidents on Threat Watch