flyto-core · Flyto2 Core: Arbitrary file write via unguarded data.*/file.* modules (incomplete fix of CVE-2026-67429)
Affects flyto-coreSource GCVE Database
Mentioned vulnerabilities
Not known to be exploited · CVSS 10.0 Critical : upgrade to 2.26.8 as a priority.
Data as of 20 Nov 2026, 01:48 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 10.0 |
|---|
- Patch
- Available – fixed in 2.26.8
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade flyto-core to 2.26.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPIflyto-core | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A patch is available in flyto-core version 2.26.8 that applies proper path validation to the affected modules, enforcing sandbox confinement. Users should upgrade to version 2.26.8 or later to remediate this vulnerability. No other mitigation is indicated as the vendor advisory confirms an official fix.
Description
Flyto-core versions prior to 2.26.8 contain a critical arbitrary file write vulnerability in several data.* and file.* modules due to incomplete path validation. These modules fail to enforce sandbox confinement, allowing an attacker with module execution privileges to write files to arbitrary absolute paths on the host. This can lead to overwriting application code, user shell configurations, cron jobs, or SSH authorized keys, resulting in remote code execution and full host compromise. The issue is an incomplete fix of a prior critical vulnerability (GHSA-2956), where path validation was applied only to a subset of modules. The vulnerability is rated critical with a CVSS score of 10. A fix is available in version 2.26.8.
References
- github.com/flytohub/flyto-core/security/advisories/GHSA-p34x-fmph-9fjx (opens in a new tab)
- github.com/flytohub/flyto-core/commit/bbb6f1cfec22fee1ea0e6ecf1129d7103c85e09f (opens in a new tab)
- github.com/flytohub/flyto-core (opens in a new tab)
- github.com/flytohub/flyto-core/releases/tag/v2.26.8 (opens in a new tab)