CVE-2026-67424: flytohub flyto-core SSRF via redirect in HTTP modules

CVE-2026-67424 · Severity: high · CVSS 8.5 · Published 2026-07-29

Flyto2 Core contains a security flaw in its HTTP modules that allows attackers to bypass security filters and access internal network resources. While the system checks the initial web address provided, it fails to re-verify the destination if that address redirects to a different location. This could allow an attacker to view sensitive internal data or cloud metadata that should be protected from external access.

Technologies: flyto-core (PyPI). Vendors: PyPI.

Quick answers

Is CVE-2026-67424 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-67424 being exploited in the wild.
How severe is CVE-2026-67424?
High severity, with a CVSS score of 8.5, published 29 July 2026.
Which products and versions are affected?
flyto-core (PyPI) <= 2.26.6, ECOSYSTEM:introduced=0,fixed=2.26.7.
Is there a fix for CVE-2026-67424?
Yes. flyto-core (PyPI): upgrade to 2.26.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-67424 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-67424?
Check whether you run flyto-core (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • flyto-core (PyPI): upgrade to 2.26.7 or later
    pip install "flyto-core>=2.26.7"

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in Flyto2 Core's HTTP modules (http.get, http.request, http.batch). While these modules utilize an SSRF guard to validate the initial URL, they rely on the aiohttp library's default behavior of automatically following redirects (allow_redirects=True) without re-validating the 'Location' header of subsequent hops. An attacker can provide a public URL that issues a 302 redirect to an internal IP address or cloud metadata service (e.g., 169.254.169.254). Because the guard only checks the first URL, the redirect is followed transparently, allowing the attacker to read internal responses. The issue is fixed in version 2.26.7 by ensuring all redirect hops are validated.

Affected products

  • flytohub flyto-core <= 2.26.6

Identifiers

  • CVE-2026-67424
  • GHSA-c9hr-64h3-gxpc
  • PYSEC-2026-3569

Timeline

  • 2026-07-08: disclosed
  • 2026-07-29: advisory: NVD publication
  • 2026-07-30: patched: GitHub Advisory published/reviewed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.