Skip to main content
CVE-2026-77313VulnerabilityPublished

flyto-core · Flyto2 Core: SSRF guard validates the resolved IP but connects by hostname, allowing DNS-rebinding TOCTOU

Affects flyto-coreSource GCVE Database

0
Compare
Authoritative record:CVE-2026-77313· High 7.1

Not known to be exploited · CVSS 7.1 High : upgrade to 2.26.8 soon.

Data as of 20 Nov 2026, 01:48 UTC

CVSS 3.1 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.17.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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 19 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 flyto-core to 2.26.8.

Affected software

ProductAffectedFixed in
PyPIflyto-coreAffected
  • <2.26.8
Fixed in
  • 2.26.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Flyto2 Core version 2.26.8 that pins the validated IP address and rejects any differing connect-time DNS resolutions, preventing the DNS rebinding TOCTOU attack. Users should upgrade to version 2.26.8 or later. No other mitigations are indicated or necessary as the vulnerability is resolved by this official fix.

Description

Flyto2 Core versions up to 2.26.6 contain a Server-Side Request Forgery (SSRF) vulnerability due to a time-of-check to time-of-use (TOCTOU) race condition in the SSRF guard. The function validate_url_ssrf resolves a hostname to an IP address and checks if it is private, but then discards the IP and returns the hostname. At connection time, aiohttp performs a fresh DNS resolution, allowing an attacker controlling DNS to alternate the resolved IP between a public and an internal IP, bypassing the SSRF guard. This enables unauthorized internal network fetches. The issue is fixed in version 2.26.8 by pinning the validated IP address for connection.

References

Community reviews

Loading reviews…