Flyto Core server-side request forgery via DNS rebinding in URL guard
Only affects flyto-core 2.26.7 and earlier with an outbound HTTP module driven by an attacker-supplied URL. Fixed in 2.26.8.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.26.8
- Who is exposed
- Specific setups only
Summary
Flyto2 Core's URL safety check can be bypassed with DNS rebinding, so an attacker who controls a hostname's DNS can make the software's outbound requests reach internal systems, including metadata services, and read the responses. An attacker with low-privilege network access can trigger this remotely, but it depends on a low DNS TTL and a timing-dependent change in DNS answers.
Written by a model
Original 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.
Who should check
Teams running flyto-core 2.26.7 or earlier (PyPI) with outbound HTTP modules such as http.get, graphql, monitor.http_check or notification modules fed attacker-influenced URLs
“all confined to v<=2.26.7”
What to do
Check whether your setup matches what the bug needs.
Attacker controls DNS for the target hostname, with low or zero TTL and a flipped answer between the guard's lookup and the connection's lookup flyto-core version 2.26.7 or earlier, with an outbound HTTP module driven by an attacker-supplied URLUpgrade to a fixed version: 2.26.8.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-77316 (Flyto2 Core: SSRF guard bypass via DNS rebinding (validate_url_ssrf resolves-then-connects without pinning)), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-77316 (entry last updated 2026-11-19):
Affected:
- flytohub flyto-core: fixed in 2.26.8
Fixed versions: 2.26.8.
Conditions (all must be true for the bug to be hit):
- Attacker controls DNS for the target hostname, with low or zero TTL and a flipped answer between the guard's lookup and the connection's lookup (source: https://github.com/flytohub/flyto-core/security/advisories/GHSA-6pm8-6f34-9v3g)
- flyto-core version 2.26.7 or earlier, with an outbound HTTP module driven by an attacker-supplied URL (source: https://github.com/flytohub/flyto-core/releases/tag/v2.26.8)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-77316 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77316 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/flytohub/flyto-core/security/advisories/GHSA-6pm8-6f34-9v3g
- https://github.com/flytohub/flyto-core/commit/bf748df864d348004cf45d830bc59f62c5c4a58a
- https://github.com/flytohub/flyto-core/releases/tag/v2.26.8
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-77316
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-77316"}.Affected versions
- flytohub flyto-corefixed in 2.26.8
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 22 if CISA's SSVC rates it automatable
Timeline
- CVE published
- First seen by cve.now
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · flytohub/flyto-core · Advisory GHSA-6pm8-6f34-9v3g |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-77316 |
| Record | NVD · CVE-2026-77316 |
| Other links 2 | |
| Repository | GitHub · flytohub/flyto-core · Commit bf748df8 |
| Repository | GitHub · flytohub/flyto-core · Release v2.26.8 |
Questions about CVE-2026-77316
Is CVE-2026-77316 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.
Source: cve.now feed data
What does this mean?
The SSRF guard in validate_url_ssrf resolves a hostname, then the connection resolves it again without pinning the address. If DNS answers differently between those two lookups, requests can reach internal or metadata services the guard is meant to block, potentially including cloud metadata credentials.
Source: github.com, github.com
Which versions are affected by CVE-2026-77316?
flyto-core: before 2.26.8.
Source: cve.now feed data
Am I affected, and how do I check?
Affected versions are flyto-core 2.26.7 and earlier, in setups with an outbound HTTP module driven by an attacker-supplied URL. To check, look at the installed flyto-core version and whether that module takes URLs from untrusted input.
Source: github.com, github.com
How do I fix CVE-2026-77316?
Upgrade flyto-core to 2.26.8, which is the listed fixed version.
Source: github.com, github.com
Related
- CVE-2026-77312Flyto2 Core: Arbitrary file write via unguarded data.*/file. modules (incomplete fix of CVE-2026-67429)
- CVE-2026-67429Flyto2 Core: Arbitrary file write via image.download (and other file-writing modules)
- CVE-2026-67426Flyto2 Core: Unauthenticated flyto-verification /run: callback_url SSRF and internal runner-secret exfiltration
- CVE-2026-67427Flyto2 Core: ${env.VAR} interpolation reads any env secret despite env.get being denylisted
- CVE-2026-67425Flyto2 Core: LLM/API keys leak to an attacker-controlled base_url
- CVE-2026-77315Flyto2 Core: http.paginate follows server-supplied next-page URLs (Link header / cursor) without SSRF revalidation
No corrections so far. Something wrong on this page? Report an error.