Loading vulnerability…
CVE-2026-67424 is a server-side request forgery vulnerability in Flyto2 Core affecting versions prior to 2.26.7. The flaw is present in the HTTP modules http.get, http.request, and http.batch, where the application validates only the initial user-supplied URL and then allows the underlying HTTP client to automatically follow redirects without revalidating each intermediate Location target. Because redirect hops are not subjected to the same SSRF policy checks as the original URL, an attacker can supply an apparently allowed public URL that issues an HTTP redirect into internal address space, including loopback, private network services, or cloud metadata services. The vulnerable behavior results in Flyto2 Core fetching the redirected internal resource and returning its response body through workflow execution output.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
An SSRF bypass vulnerability in Flyto2 Core where the application validates the initial URL but fails to revalidate intermediate HTTP redirect targets, allowing access to internal services and cloud metadata endpoints.
A high-severity SSRF vulnerability in Flyto2 Core where HTTP modules validate only the initial URL and then follow redirects without revalidating each hop, allowing access to internal address space and disclosure of internal response bodies.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.