Skip to main content
CVE-2026-77315VulnerabilityPublished

flyto-core · Flyto2 Core: http.paginate follows server-supplied next-page URLs (Link header / cursor) without SSRF revalidation

Affects flyto-coreSource GCVE Database

0
Compare
Authoritative record:CVE-2026-77315· High 8.5

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

Data as of 20 Nov 2026, 01:48 UTC

CVSS 3.1 base score
8.5High
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.18.5
Patch
Available – fixed in 2.26.8
CVSS:3.1/AV:N/AC:L/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 patch is available in Flyto2 Core version 2.26.8 that fixes this vulnerability by enforcing validation on every follow-up pagination URL before fetching it. Users should upgrade to version 2.26.8 or later. Until patched, users should avoid using http.paginate with untrusted sources or ensure additional validation of pagination URLs. No other vendor advisories indicate that no action is required or that this is already mitigated.

Description

Flyto2 Core's http.paginate function validates only the initial base URL before following server-supplied pagination URLs from Link headers or cursor/offset URLs without revalidating them. This allows an attacker to craft a first-page response that points the 'next' URL to an internal address, causing a second-order SSRF. The internal response body is aggregated and returned to the caller, exposing sensitive internal information. Versions up to 2.26.6 are affected, with a fix available in version 2.26.8.

References

Community reviews

Loading reviews…