CVE-2026-67424
SSRF via HTTP redirect handling in Flyto2 Core (<2.26.7).
Is CVE-2026-67424 being exploited?
Not confirmed. CVE-2026-67424 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.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-67424?
CVE-2026-67424 is rated High with a CVSS score of 8.5. 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-67424?
Yes. A fix has been recorded for CVE-2026-67424. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-67424 affect?
CVE-2026-67424 affects Flyto2 Core < 2.26.7, http.get module, http.request module, http.batch module, and 1 further product or version. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-67424?
Upgrade to Flyto2 Core 2.26.7; block redirects to private IP ranges and restrict workflow URLs.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote SSRF: attacker-supplied public URL can redirect to internal addresses and return internal response bodies.
Patch when possible
- 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.