CVE-2026-67428: Flyto2 Core SSRF in multiple HTTP-emitting modules

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

Flyto2 Core, a framework for building AI workflows, contains a security flaw where several of its communication modules fail to verify the destination of web requests. An authorized user could exploit this to force the system to connect to internal servers or cloud management interfaces that should be private. This could lead to the theft of sensitive cloud credentials or unauthorized access to internal company data and services.

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

Quick answers

Is CVE-2026-67428 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-67428 being exploited in the wild.
How severe is CVE-2026-67428?
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-67428?
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-67428 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-67428?
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 multiple Flyto2 Core modules, including core.api.http_get, graphql.query, and various notification handlers. While the project includes an SSRF guard (validate_url_with_env_config), these specific modules bypass it, relying instead on an inert metadata tag. An authenticated attacker with workflow-author privileges can provide a malicious URL (e.g., 169.254.169.254 or 127.0.0.1) to the affected modules. Because the full response body is returned to the caller, this enables the theft of IAM credentials from cloud metadata services and read/write access to internal APIs. The issue is fixed in version 2.26.7.

Affected products

  • flytohub flyto-core <= 2.26.6

Identifiers

  • CVE-2026-67428
  • GHSA-pgwh-4jj4-qm8v
  • PYSEC-2026-3572

Timeline

  • 2026-07-08: disclosed
  • 2026-07-29: advisory: NVD publication
  • 2026-07-30: patched: GitHub Advisory published/updated with patch version 2.26.7

References

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