Skip to main content
Menu
CVEs

Flyto Core SSRF guard bypass via DNS rebinding race condition

CVE-2026-77313Published November 19, 2026, updated

7.1HighCNA
Exploited
No known exploitation
Fix
Fixed in 2.26.8
Who is exposed
Specific setups only

Summary

The flyto-core software from flytohub has a flaw in its SSRF guard: it checks the IP address from one DNS lookup but connects using a separate lookup, so the address can change between the two. A remote attacker with low-privilege access who controls DNS for a hostname can bypass the guard and read internal or metadata-service responses, but only by winning a timing-dependent change in the DNS answer.

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 resolves and checks a hostname but returns the hostname URL rather than the validated address, and session.get in http.get performs an independent DNS lookup when connecting. A low-privileged caller with control of the hostname's DNS can make the first lookup return a public address and the connection-time lookup return an internal address, bypassing the SSRF guard for all modules that call it and exposing readable internal or metadata-service responses. Successful exploitation requires attacker-controlled DNS and a successful timing-dependent answer change between the two lookups. This issue is fixed in version 2.26.8.

What to do

Upgrade 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-77313 (Flyto2 Core: SSRF guard validates the resolved IP but connects by hostname, allowing DNS-rebinding TOCTOU), 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-77313 (entry last updated 2026-11-19):
Affected:
- flytohub flyto-core: fixed in 2.26.8
Fixed versions: 2.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-77313 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77313 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-pfg2-w999-497v
- 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-77313
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-77313"}.

Affected versions

cve.now Index

15Pof 100 · provisional · methodology v3
  • 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

  1. CVE published
  2. First seen by cve.now

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · flytohub/flyto-core · Advisory GHSA-pfg2-w999-497v
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-77313
RecordNVD · CVE-2026-77313
Other links 2
RepositoryGitHub · flytohub/flyto-core · Commit bf748df8
RepositoryGitHub · flytohub/flyto-core · Release v2.26.8

Questions about CVE-2026-77313

Is CVE-2026-77313 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

Which versions are affected by CVE-2026-77313?

flyto-core: before 2.26.8.

Source: cve.now feed data

How do I fix CVE-2026-77313?

Upgrade to a fixed version: 2.26.8.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.