CVE-2026-67424

Received Received - Intake

HTTP Redirect Bypass in Flyto2 Core

Publication date: 2026-07-29

Last updated on: 2026-07-29

Assigner: GitHub, Inc.

Description

Flyto2 Core is an execution kernel for automation and AI-agent workflows. Prior to 2.26.7, the HTTP modules http.get, http.request, and http.batch in src/core/modules/atomic/http/get.py, src/core/modules/atomic/http/request.py, and src/core/modules/atomic/http/batch.py validate only the initial URL, then follow redirects with allow_redirects=True and without per-hop Location revalidation, allowing a public URL to redirect into internal address space and return the internal response body. This issue is fixed in version 2.26.7.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-07-29

Last Modified

2026-07-29

Generated

2026-07-30

AI Q&A

2026-07-30

EPSS Evaluated

N/A

NVD

CVE-2026-67424

Affected Vendors & Products

Vendor	Product	Version / Range
flyto2	core	to 2.26.7 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-918	The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.

Attack-Flow Graph

Executive Summary

The vulnerability in Flyto2 Core before version 2.26.7 involves improper handling of HTTP redirects. The http.get, http.request, and http.batch modules validate only the initial URL and then follow redirects without revalidating the Location header for each hop. This allows a public URL to redirect to an internal address, potentially exposing internal response bodies.

Detection Guidance

The vulnerability involves HTTP modules following redirects without validating the final URL, potentially exposing internal responses. Monitor network traffic for unusual redirects from public to internal addresses. Check logs for http.get, http.request, or http.batch calls with redirect chains ending in internal IP ranges.

Impact Analysis

This vulnerability could allow attackers to access internal network resources or sensitive data by tricking the system into following malicious redirects. It may lead to unauthorized information disclosure, data breaches, or internal service exposure if exploited.

Compliance Impact

This vulnerability could lead to violations of GDPR or HIPAA by exposing sensitive data through unauthorized access. GDPR requires protecting personal data, while HIPAA mandates safeguarding protected health information. Exploitation may result in non-compliance penalties.

Mitigation Strategies

Upgrade Flyto2 Core to version 2.26.7 or later. If upgrading is not immediately possible, disable redirects in HTTP modules by setting allow_redirects=False and manually handle redirects with strict URL validation.

Hi! I’m here to help you understand CVE-2026-67424. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70