CVE-2026-67425
Environment API keys exfiltrated to attacker-controlled base_url via llm.chat (SSRF).
Is CVE-2026-67425 being exploited?
Not confirmed. CVE-2026-67425 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.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-67425?
CVE-2026-67425 is rated High with a CVSS score of 8.6. 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-67425?
Yes. A fix has been recorded for CVE-2026-67425. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67425 affect?
CVE-2026-67425 affects Flyto2 Core < 2.26.6, llm.chat module, Deployments exposing caller-controlled base_url. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67425?
Upgrade to Flyto2 Core 2.26.6 and rotate any exposed API keys immediately
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Disclosure of OPENAI/ANTHROPIC API keys via Authorization header to attacker-controlled base_url, enabling account takeover, data access, and billing abuse.
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.