CVE-2026-67426
Unauthenticated SSRF and runner-secret exfiltration in Flyto2 verification service
Is CVE-2026-67426 being exploited?
Not confirmed. CVE-2026-67426 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.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-67426?
CVE-2026-67426 is rated Critical with a CVSS score of 9.3. 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-67426?
Yes. A fix has been recorded for CVE-2026-67426. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67426 affect?
CVE-2026-67426 affects Flyto2 Core <2.26.7, flyto-verification service (port 8344), AI-agent automation workflows using Flyto2. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67426?
Upgrade Flyto2 Core to 2.26.7 immediately; restrict network access to verification service
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated attacker can trigger outbound POST to attacker-controlled callback_url, exfiltrate X-Internal-Key (runner secret) and perform SSRF into internal services.
Immediate action required
- affected< 2.26.7
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.