Summary
flyto-core up to version 2.26.7 allows several data.* and file.* modules to write files to client-controlled paths outside the configured sandbox directory. The vendor fixed the issue in version 2.26.8.
What happened
According to the advisory, several flyto-core file-writing modules do not apply the path validation that confines writes to the sandbox directory (FLYTO_SANDBOX_DIR). Named modules are data.csv.write, data.json_to_csv, file.copy and file.move, along with other data.*, file.* and report-writer families that also do not call that validation. data.csv.write only rejects paths containing "..", which does not block absolute paths; the other named modules perform no path check at all. A client able to run a module or recipe through the MCP server or recipe engine can therefore write content of its choosing to a path of its choosing outside the sandbox. The stated root cause is that the earlier fix (GHSA-2956-977x-2w3r, released in v2.26.6) added the validation module by module to a specific list instead of enforcing it centrally, leaving modules not on that list unconfined. The weakness is classified as CWE-22 (path traversal).
Why it matters
The advisory states that overwriting files such as application code, recipes or system startup configuration files could lead to code execution and host compromise, the same impact for which the earlier vulnerability was rated critical. The source assigns critical severity and a CVSS 3.1 score of 10.0 (vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:H, per GHSA). The advisory's own descriptive text also gives a different assessment (9.3, with PR:L and C:H) and notes that on the HTTP surface of the MCP server access is unauthenticated, per CVE-2026-77312 and a reference to CVE-2026-55786. The source does not indicate any active exploitation.
Affected products and versions
flyto-core (PyPI package flyto-core): versions <= 2.26.7. Fixed version: 2.26.8. Identifiers: CVE-2026-77312, GHSA-p34x-fmph-9fjx.
| Product | Versions | Fixed in |
|---|---|---|
| flyto-core | <= 2.26.7 | 2.26.8 |
| flytohub flyto-core | < 2.26.8 | — |
Action recommended by the source
The vendor lists version 2.26.8 as the release that fixes the issue (published in the flytohub/flyto-core repository, with an associated fix commit). The source does not mention alternative mitigations.
Fixed in: 2.26.8
Sources and references
- https://github.com/advisories/GHSA-p34x-fmph-9fjx — GHSA
- https://github.com/flytohub/flyto-core/security/advisories/GHSA-p34x-fmph-9fjx — GHSA
- https://github.com/flytohub/flyto-core/commit/bbb6f1cfec22fee1ea0e6ecf1129d7103c85e09f — GHSA
- https://github.com/flytohub/flyto-core/releases/tag/v2.26.8 — GHSA
- https://github.com/advisories/GHSA-h9f9-h6gm-wc85 — CVE Program
Weaknesses (CWE): CWE-22
Relevant change history
Published
Advisory published.