SSRF in Flytohub Flyto-Core
CVE-2026-77316
- CVSS v3
- 7.1 High
- Public exploits
- 1 repository
- EPSS
- 0.003 · 29.1th percentile
- Published
- 2026-11-19
What to do
- Fixed in
2.26.8- Affected
- 1 affected product
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 validates one DNS answer and then returns the hostname, while guarded_aiohttp_request(), enforce_outbound_url(), and validate_url_with_env_config() allow the outbound connection to perform an independent second lookup. A caller with control of the hostname's DNS can make validation see a public address and make the connection see an internal address, bypassing the guard across its outbound consumers and exposing readable internal or metadata-service responses. The attack requires low or zero DNS TTL behavior and a successful timing-dependent answer change; static multiple-address answers are checked and do not provide the same bypass. This issue is fixed in version 2.26.8.
Vulnerability class: SSRF (Server-Side Request Forgery)
Published .
CVSS v3 metric
CVSS v3 base score 7.1 (High). Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N.
- Attack Vector
- Network
AV:N - Attack Complexity
- High
AC:H - Privileges Required
- Low
PR:L - User Interaction
- None
UI:N - Scope
- Changed
S:C - Confidentiality
- High
C:H - Integrity
- Low
I:L - Availability
- None
A:N
EPSS exploit prediction
EPSS 0.003, 29.1th percentile (last changed ). About EPSS.
Affected products
- Flytohub Flyto-Core — versions < 2.26.8
Weakness classification (CWE)
Public exploits and proof-of-concept code
1 public repository with exploit or proof-of-concept code for this CVE:
- googlesky/CVE-2026-77316 (last pushed 2026-11-21): flyto-core <=2.26.7 SSRF-guard hardening incomplete: validate_url_ssrf discarded the resolved IP, aiohttp re-resolved at connect; TTL-0 DNS flips public to internal, attacker service hands metadata c…