Skip to main content

CVE-2026-77313flytohub flyto-core time-of-check to time-of-use race

Schedule itHigh7.1EPSS not scored yet

CVE-2026-77313 is a time-of-check to time-of-use race in flytohub flyto-core, rated high (7.1 on CVSS 3.1).

Why this priority: High severity, with no exploitation signal yet.

Published · Updated · NVD status: Received

What it is

Something is checked, then changed by an attacker before it is used. The server can be made to fetch an address of the attacker's choosing, including internal services and cloud metadata endpoints.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything. Success also depends on conditions the attacker does not fully control.

What an attacker gains

A successful attack can read the data it protects. In practice, this kind of flaw lets an attacker win a timing window to bypass a check or corrupt shared state. The damage can spread past the vulnerable component into others.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Upgrade flytohub flyto-core to 2.26.8 or later.
  2. Until it is patched, review who holds accounts that can reach it.

Description from NVD

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 this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Request handlers and jobs that share state. The flaw sits between concurrent requests or processes.
  • Services that fetch URLs or call other hosts for a caller. The flaw sits between the application and the internal network behind it.

Trust boundaries in play

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • Isolation between components. The impact crosses out of the vulnerable component into others it should be isolated from.
  • Between concurrent requests or processes. An attacker who crosses it can win a timing window to bypass a check or corrupt shared state.
  • Between the application and the internal network behind it. An attacker who crosses it can make the server send requests into internal networks or cloud metadata.

Questions to answer about your own systems

  • Where does flytohub flyto-core run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.