flyto-core patch for critical file-write flaw leaves data and file modules open
GitHub's advisory describes CVE-2026-77312, an arbitrary file write in flyto-core 2.26.7 and earlier that it calls an incomplete fix of an earlier critical flaw. The advisory says version 2.26.8 contains the fix. Exploitation status is not stated.
The GitHub Advisory Database published GHSA-p34x-fmph-9fjx, tracked as CVE-2026-77312, describing an arbitrary file write in the flyto-core Python package. The advisory says versions up to and including 2.26.7 are affected and that 2.26.8 contains the fix. [1]
The advisory calls this an incomplete fix of GHSA-2956-977x-2w3r, which was patched in v2.26.6. According to the advisory, that earlier fix added path validation only to a fixed list of modules, and the data and file write modules were left out. [1]
The advisory names data.csv.write, data.json_to_csv, file.copy and file.move as modules that accept client-supplied absolute paths without confinement to the sandbox directory. It says the result could be overwriting of files such as shell startup files or authorized_keys, which it links to code execution. [1]
The advisory rates the issue critical, with a CVSS v3.1 score of 9.3. Its GitHub severity field, however, lists a CVSS score of 10. The advisory does not explain the difference. [1]
The advisory says a client able to run modules through the recipe engine or the MCP execute_module endpoint can trigger the flaw, and that it requires low privileges. [1]
Caveat: these details come from the advisory alone. TechDots has not found independent confirmation of the flaw, and the advisory does not state whether it has been exploited. [1]
What we couldn't confirm
- No named source states exploitation status, and TechDots has found no reports of exploitation in the wild.
- The advisory's CVSS 9.3 score conflicts with the GitHub severity field's CVSS 10; the reason is not explained.
- No independent researcher, vendor or government source has confirmed the flaw beyond the advisory.
- The advisory refers to unauthenticated HTTP MCP exposure under CVE-2026-55786, but that advisory was not among the sources reviewed.
- No response from the flyto-core maintainers was available at the time of writing.
Sources
- GitHub Advisory Database: GHSA-p34x-fmph-9fjx (CVE-2026-77312): Flyto2 Core: Arbitrary file write via unguarded data.*/file.* modules (incomplete fix of CVE-2026-67429)Source published · TechDots found it
Statements labelled as a company's claim have not been independently confirmed by TechDots.
Get Cybersecurity stories by email
Related coverage
nginx2root: five new nginx bugs, patch now and lock origins to Cloudflare
F5 and nginx.org disclosed ten nginx vulnerabilities on November 18, 2026. Five memory corruption flaws, named nginx2root by Xint, can crash workers or run commands, and one HTTP/2 bug is the most widespread. Cloudflare says its edge is unaffected and that its proxy shields origins from the HTTP/2 and HTTP/3 attacks, but patching is still required.
Etherpad pre-auth file read flaw rated critical in GitHub advisory
GitHub Advisory Database has published an advisory for an unauthenticated file-read flaw in Etherpad's /static/* handler, affecting ep_etherpad-lite versions 1.8.14 up to 3.3.3 and fixed in 3.3.3. The advisory rates it critical, CVSS 9.8.