Flyto2 Core: Guarded HTTP modules follow redirects into internal space without per-hop SSRF revalidation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.5 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:L/A:N

EPSS

• CVE-2026-67424: 0.29% estimated exploitation activity in the next 30 days; percentile 22.02 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary The HTTP modules that DO call the SSRF guard (http.get, http.request, http.batch) validate only the initial URL, then issue the request with aiohttp's default allowredirects=True and perform no per-hop revalidation. An attacker hosts a public URL that 302-redirects to an internal address; the guard passes on the public host and aiohttp transparently follows the redirect into internal space, returning the internal body. Root Cause src/core/modules/atomic/http/get.py:116 calls session.get(url, ...) with no allowredirects argument → aiohttp default True. request.py:60 sets allowredirects=followredirects (default True at :327); batch.py:57 likewise. A repo grep of http/ for onrequestredirect / response.history returns NONE — there is no redirect interception or Location revalidation. Impact Full readable SSRF that defeats the primary SSRF control on the very modules that correctly validate. Confidentiality of internal/metadata responses (C:H), S:C. Proof of Concept Verified live:…

Published by the source

30 Jul 2026, 14:48 UTC

Last modified by the source

30 Jul 2026, 14:48 UTC

Source last checked

26 Oct 2026, 13:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-c9hr-64h3-gxpc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-67424

Advisory: Flyto2 Core: Guarded HTTP modules follow redirects into internal space without per-hop SSRF revalidation
IDs: CVE-2026-67424, GHSA-c9hr-64h3-gxpc
Record: https://patchnext.com/advisories/cve-2026-67424 (revision 1, source checked 26 Oct 2026, 13:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: flyto-core 2.26.7. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI flyto-core: affected <= 2.26.6; fixed in 2.26.7

## Suggested inspection (read-only)
- `python -m pip show flyto-core`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on flyto-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-c9hr-64h3-gxpc (GitHub-reviewed advisory GHSA-c9hr-64h3-gxpc lists affected ranges: PyPI flyto-core >=0 <=2.26.6)

Commands are suggestions: review each one before running it.