CVE Explore

SSRF in Flytohub Flyto-Core

CVE-2026-77313

CVSS v3
7.1 High
Public exploits
1 repository
EPSS
0.003 · 21.0th 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 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.

Vulnerability class: TOCTOU (Time-of-Check to Time-of-Use)

Published · last modified .

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, 21.0th percentile (last changed ). About EPSS.

Affected products

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-77313 (last pushed 2026-11-21): flyto-core <=2.26.7: validate_url_ssrf discarded the resolved IP and aiohttp re-resolved at connect — TTL-0 DNS answers public for the guard, internal for the connection, guard bypassed on every cons…

References