CVE-2026-77313

GHSA-pfg2-w999-497v · published 19 Nov 2026 · updated 20 Nov 2026

Flyto2 Core: SSRF guard validates the resolved IP but connects by hostname, allowing DNS-rebinding TOCTOU

7.1HighCVSS 7.1EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in flyto-core 2.26.8.

Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, validate_url_ssrf in src/core/utils.py resolves and checks a hostname but returns the hostname URL rather than the validated address, and session.get in http.get performs an independent DNS lookup when connecting. A low-privileged caller with control of the hostname's DNS can make the first lookup return a public address and the connection-time lookup return an internal address, bypassing the SSRF guard for all modules that call it and exposing readable internal or metadata-service responses. Successful exploitation requires attacker-controlled DNS and a successful timing-dependent answer change between the two lookups. This issue is fixed in version 2.26.8.

Affected

Vendors, products and packages with version ranges

VendorProductVersionsFixed
flytohub<2.26.8
pypi: flyto-core<2.26.8, <=2.26.72.26.8

Timeline

Every event on this vulnerability

Related

Other vulnerabilities in flyto-core (PyPI), strongest first

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-77313 severity on Zeptric[![CVE-2026-77313](https://zeptric.io/badge/cve/CVE-2026-77313.svg)](https://zeptric.io/cve/CVE-2026-77313)