Flyto Core arbitrary file write in data and file modules
Affects flyto-core 2.26.7 and earlier. Fixed in 2.26.8.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.26.8
- Who is exposed
- Not reported
Summary
Flyto2 Core has a flaw in several file-writing modules that lets an attacker write files outside the configured sandbox, potentially overwriting application code, recipes, or startup and scheduled-task files to run code on the host. An attacker can reach it remotely, without logging in or any user action, as long as they can run modules or recipes.
Written by a model
Original description
Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, the earlier CVE-2026-67429 remediation applied validate_path_with_env_config() to only a hand-picked set of file-writing modules, leaving data.csv.write in src/core/modules/atomic/data/csv_write.py, data.json_to_csv in src/core/modules/atomic/data/json_to_csv.py, file.copy in src/core/modules/atomic/file/copy.py, and file.move in src/core/modules/atomic/file/move.py outside the FLYTO_SANDBOX_DIR confinement boundary. The advisory also identifies unguarded modules across the broader data., file., and report-writer families. data.csv.write relies on a .. substring denylist that does not reject absolute paths, while the other named modules accept caller-controlled output or destination paths without the canonical guard. A caller able to execute modules or recipes can therefore write attacker-controlled content outside the configured sandbox, potentially overwriting application code, recipes, startup files, scheduled-task files, or authorization files and gaining code execution on the host. This issue is fixed in version 2.26.8.
Who should check
Teams running flyto-core (pip) 2.26.7 or earlier, especially those exposing MCP execute_module or the recipe engine to any client.
“Affected versions <= 2.26.7”
What to do
Upgrade to a fixed version: 2.26.8.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-77312 (Flyto2 Core: Arbitrary file write via unguarded data.*/file. modules (incomplete fix of CVE-2026-67429)), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-77312 (entry last updated 2026-11-19):
Affected:
- flytohub flyto-core: fixed in 2.26.8
Fixed versions: 2.26.8.
Conditions (all must be true for the bug to be hit):
- Affected flyto-core versions are 2.26.7 and earlier (fixed in 2.26.8). (source: https://github.com/flytohub/flyto-core/security/advisories/GHSA-p34x-fmph-9fjx)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-77312 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77312 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/flytohub/flyto-core/security/advisories/GHSA-p34x-fmph-9fjx
- https://github.com/flytohub/flyto-core/commit/bbb6f1cfec22fee1ea0e6ecf1129d7103c85e09f
- https://github.com/advisories/GHSA-h9f9-h6gm-wc85
- https://github.com/flytohub/flyto-core/releases/tag/v2.26.8
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-77312
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77312"}.Affected versions
- flytohub flyto-corefixed in 2.26.8
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity10/10CVSS 10.0
- No patch0/5No signal
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 32 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Evidence 6
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · flytohub/flyto-core · Advisory GHSA-p34x-fmph-9fjx |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-77312 |
| Record | NVD · CVE-2026-77312 |
| Other links 3 | |
| Advisory | GitHub Advisory Database · Advisory GHSA-h9f9-h6gm-wc85 |
| Repository | GitHub · flytohub/flyto-core · Commit bbb6f1cf |
| Repository | GitHub · flytohub/flyto-core · Release v2.26.8 |
Questions about CVE-2026-77312
Is CVE-2026-77312 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
Flyto2 Core's data.*/file. modules do not restrict file paths, so an attacker-controlled path and content can write files outside FLYTO_SANDBOX_DIR. Overwritten files could include application code, recipes, startup files, or authorization files, which could lead to code execution on the host. This CVE is an incomplete fix of CVE-2026-67429.
Source: github.com
Which versions are affected by CVE-2026-77312?
flyto-core: before 2.26.8.
Source: cve.now feed data
Am I affected, and how do I check?
flyto-core versions 2.26.7 and earlier are affected. To check an installed copy, look up its flyto-core version and compare it with 2.26.7.
Source: github.com
How do I fix CVE-2026-77312?
Upgrade flyto-core to version 2.26.8 or later, which is the fixed version listed for this vulnerability.
Source: github.com
Related
- CVE-2026-67429Flyto2 Core: Arbitrary file write via image.download (and other file-writing modules)
- CVE-2026-67426Flyto2 Core: Unauthenticated flyto-verification /run: callback_url SSRF and internal runner-secret exfiltration
- CVE-2026-67427Flyto2 Core: ${env.VAR} interpolation reads any env secret despite env.get being denylisted
- CVE-2026-67425Flyto2 Core: LLM/API keys leak to an attacker-controlled base_url
- CVE-2026-77315Flyto2 Core: http.paginate follows server-supplied next-page URLs (Link header / cursor) without SSRF revalidation
- CVE-2026-67428Flyto2 Core: Multiple HTTP-family modules fetch client-controlled URLs without the SSRF guard their siblings apply (SSRF to internal/metadata)
No corrections so far. Something wrong on this page? Report an error.