CVE-2026-77316: flytohub flyto-core · Server-Side Request Forgery
Affects flytohub flyto-coreSource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 2.26.8 soon.
Data as of 19 Nov 2026, 22:05 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.1 |
|---|
- Patch
- Available – fixed in 2.26.8
CVSS:3.1/AV:N/AC:H/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
|
Description
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.