CVE-2026-67424 Flyto2 Core: Guarded HTTP modules follow redirects into internal space without per-hop SSRF revalidation
Attackers can exploit redirect handling in Flyto2 Core HTTP modules to access internal network resources and read sensitive data.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-67424?
CVE-2026-67424 is a high-severity server-side request forgery vulnerability in flytohub flyto-core, published on 29 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.7, the HTTP modules http.get, http.request, and http.batch in src/core/modules/atomic/http/get.py, src/core/modules/atomic/http/request.py, and src/core/modules/atomic/http/batch.py validate only the initial URL, then follow redirects with allow_redirects=True and without per-hop Location revalidation, allowing a public URL to redirect into internal address space and return the internal response body. This issue is fixed in version 2.26.7.
Weakness: CWE-918
Which versions are affected by CVE-2026-67424?
3 open source packages ship an affected version, including flyto-core.
| Package | Affected | Fixed in |
|---|---|---|
flyto-core PyPI | All versions | 2.26.7 |
flyto-core PyPI | All versions | 2.26.7 |
flyto-core PyPI | All versions | 2.26.7 |
How do I fix CVE-2026-67424?
Upgrade flyto-core to 2.26.7 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-67424 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67424 exists.
Sources
Also known as GHSA-c9hr-64h3-gxpc, PYSEC-2026-3569.