Flytohub flyto-core
Flyto2 Core: SSRF guard validates the resolved IP but connects by hostname, allowing DNS-rebinding TOCTOU
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- < 2.26.8
Fixed in 2.26.8
Mitigation
Upgrade flyto-core to 2.26.8 or later.
References
- Vendor advisory github.com/flytohub/flyto-core/security/adviso…
- Patch github.com/flytohub/flyto-core/commit/bf748df8…
- Release notes github.com/flytohub/flyto-core/releases/tag/v2…
Timeline
Days relative to CVE publicationFirst public PoC 1.4 days after publication; not in CISA KEV. First PoC: googlesky/CVE-2026-77313 (created 21 Nov 2026, found by us: 21 Nov 2026).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Found by us | Stars | Assessment |
|---|---|---|---|---|
| googlesky/CVE-2026-77313 | 21 Nov 2026 +1.4 d | 21 Nov 2026 | 0 | Scanner |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.