Skip to main content
Menu
CVEs

Flyto Core server-side request forgery in http.paginate

Only affects flyto-core 2.26.7 and earlier when http.paginate uses the link_header strategy, which follows the server's Link rel="next" header. Fixed in 2.26.8.

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

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

Summary

Flyto2 Core's http.paginate function follows next-page URLs supplied by a remote server without rechecking them against its SSRF protection. An attacker with low-level access can exploit this over the network to direct a follow-up request at internal or metadata services. The response from that internal service is readable and gets included in the results returned to the attacker.

Written by a model

Original description

Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.8, http.paginate in src/core/modules/atomic/http/paginate.py validates only the initial base_url, and _paginate_link_header then follows a server-supplied Link: rel="next" URL without calling the SSRF guard again. A low-privileged caller can make an allowed first page point the next request at an internal or metadata service, causing a readable second-order SSRF whose response body is aggregated into all_items and returned. This issue is fixed in version 2.26.8.

Who should check

Teams running flyto-core 2.26.7 or earlier, especially those using http.paginate with Link-header pagination in automation or AI-agent workflows

“all confined to v<=2.26.7”

github.com

What to do

  1. Check whether your setup matches what the bug needs.

    flyto-core 2.26.7 or earlier (fixed in 2.26.8) http.paginate is run with the link_header strategy, so the server's Link: rel="next" header is followed
  2. 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-77315 (Flyto2 Core: http.paginate follows server-supplied next-page URLs (Link header / cursor) without SSRF revalidation), 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-77315 (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):
- flyto-core 2.26.7 or earlier (fixed in 2.26.8) (source: https://github.com/flytohub/flyto-core/releases/tag/v2.26.8)
- http.paginate is run with the link_header strategy, so the server's Link: rel="next" header is followed (source: https://github.com/flytohub/flyto-core/security/advisories/GHSA-2mr3-rxrq-238c)
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-77315 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-77315 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-2mr3-rxrq-238c
- https://github.com/flytohub/flyto-core/commit/bbb6f1cfec22fee1ea0e6ecf1129d7103c85e09f
- 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-77315
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-77315"}.

Affected versions

cve.now Index

17Pof 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
  • Severity8.5/10CVSS 8.5
  • No patch0/5No signal

What would change the score

  • Would score about 67 if added to CISA KEV
  • Would score about 62 if CISA's SSVC rates exploitation active
  • Would score about 24 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-2mr3-rxrq-238c
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-77315
RecordNVD · CVE-2026-77315
Other links 2
RepositoryGitHub · flytohub/flyto-core · Commit bbb6f1cf
RepositoryGitHub · flytohub/flyto-core · Release v2.26.8

Questions about CVE-2026-77315

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

What does this mean?

http.paginate follows next-page URLs supplied by the server, such as a Link header or cursor, without SSRF revalidation. An attacker-controlled next-page URL can make the server fetch internal or metadata addresses, and the response body is returned to the caller in the aggregated items.

Source: github.com, github.com

Which versions are affected by CVE-2026-77315?

flyto-core: before 2.26.8.

Source: cve.now feed data

Am I affected, and how do I check?

flyto-core 2.26.7 and earlier are affected when http.paginate runs with the link_header strategy, so the server's Link: rel="next" header is followed. To check, look at the installed flyto-core version and at whether http.paginate calls use strategy link_header.

Source: github.com, github.com

How do I fix CVE-2026-77315?

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

Source: github.com, github.com

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