CVE-2026-77315

Flyto pagination could follow a next-page link into internal services

flytohub · Flyto2 Core · agent workflow runtime

First documented disclosure · Review checkpoint

Summary

An allowed first response could redirect pagination to a forbidden destination.

Severity and exploitation evidence

High · 8.5/10 · CVSS 3.1. Severity source.

Exploitation not established: Reviewed public sources describe the weakness, a correction or a controlled demonstration; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

The pagination loop does not revalidate server-supplied next-page URLs.

Conditions required

A low-privileged module caller controls the first-page response or its next-page link.

Potential impact

Internal response data can be included in returned results.

Affected versions and configurations

Before 2.26.8.

Fix and mitigation status

2.26.8.

Practical next steps

Upgrade to 2.26.8 and verify the applicable path or outbound-network controls.

Operating lesson

Revalidate every pagination and redirect target.

Evidence and limits

Original July 11 advisory predates November 19 CNA ingestion. Reviewed correction and 2.26.8 tagged utilities establish the guarded resolver; public demonstrations are not malicious exploitation. CNA publication is 2026-11-19; this is distinct from the earliest reviewed public source and correction dates. GitHub_M assessments: CVSS 3.1 8.5.

Sources