CVE-2026-67429
Arbitrary file write in Flyto2 Core via unvalidated output_dir (pre-2.26.6).
Is CVE-2026-67429 being exploited?
Not confirmed. CVE-2026-67429 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.49% probability of exploitation in the next 30 days.
How severe is CVE-2026-67429?
CVE-2026-67429 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-67429?
Yes. A fix has been recorded for CVE-2026-67429. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67429 affect?
CVE-2026-67429 affects Flyto2 Core < 2.26.6, image.download and file-writing modules. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67429?
Upgrade to Flyto2 Core 2.26.6; restrict file permissions and enforce sandboxing.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Attacker can write attacker-controlled files to any path the process can access, enabling code injection, persistence, or remote code execution.
Immediate action required
- affected< 2.26.6
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.