CVE-2026-77315: flytohub flyto-core · Server-Side Request Forgery
Affects flytohub flyto-coreSource CVE Database V5
Not known to be exploited · CVSS 8.5 High : upgrade to 2.26.8 soon.
Data as of 19 Nov 2026, 21:52 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 8.5 |
|---|
- Patch
- Available – fixed in 2.26.8
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 19 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.
What to do
Upgrade flytohub flyto-core to 2.26.8.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| flytohubflyto-core | Affected
| Fixed in
|
AI-suggested
Upgrade flyto-core to version 2.26.8 or later, where the SSRF vulnerability is fixed by proper validation of subsequent Link: rel="next" URLs in the pagination logic. No other mitigation is indicated by the vendor advisory.
Description
CVE-2026-77315 is a server-side request forgery (SSRF) vulnerability in flytohub's flyto-core execution kernel for automation and AI-agent workflows. Versions prior to 2.26.8 improperly validate only the initial base URL in the http.paginate module, allowing a low-privileged user to manipulate subsequent requests via server-supplied Link headers. This leads to a second-order SSRF where internal or metadata service responses can be read and aggregated. The issue is fixed in version 2.26.8.