SSRF in Flytohub Flyto-Core
CVE-2026-77315
- CVSS v3
- 8.5 High
- Public exploits
- 1 repository
- EPSS
- 0.004 · 30.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, http.paginate in src/core/modules/atomic/http/paginate.py validates only the initial base_url, and _paginate_link_header then follows a server-supplied Link: rel="next" URL without calling the SSRF guard again. A low-privileged caller can make an allowed first page point the next request at an internal or metadata service, causing a readable second-order SSRF whose response body is aggregated into all_items and returned. This issue is fixed in version 2.26.8.
Vulnerability class: SSRF (Server-Side Request Forgery)
Published · last modified .
CVSS v3 metric
CVSS v3 base score 8.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N.
- Attack Vector
- Network
AV:N - Attack Complexity
- Low
AC:L - 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.004, 30.0th 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-77315 (last pushed 2026-11-21): flyto-core <=2.26.7: http.paginate followed server-supplied Link rel=next with no revalidation — attacker page-1 redirects the loop at internal space, body aggregated into items (second-order SSRF)…