Flytohub flyto-core
Flyto2 Core: http.paginate follows server-supplied next-page URLs (Link header / cursor) without SSRF revalidation
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.
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/bbb6f1cf…
- 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-77315 (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-77315 | 21 Nov 2026 +1.4 d | 21 Nov 2026 | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.