CVE-2025-69226: PYSEC-2026-1097 - AIOHTTP vulnerable to brute-force leak of internal static file path components

CVE-2025-69226 · Severity: medium · CVSS 5.3 · Published 2026-01-05

AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. Versions 3.13.2 and below enable an attacker to ascertain the existence of absolute path components through the path normalization logic for static files meant to prevent path traversal. If an application uses web.static() (not recommended for production deployments), it may be possible for an attacker to ascertain the existence of path components. This issue is fixed in version 3.13.3.

Technologies: Aiohttp, aiohttp (PyPI). Vendors: Aiohttp, PyPI.

Quick answers

Is CVE-2025-69226 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2025-69226 being exploited in the wild.
How severe is CVE-2025-69226?
Medium severity, with a CVSS score of 5.3, published 5 January 2026.
Which products and versions are affected?
aiohttp (PyPI) ECOSYSTEM:introduced=0,fixed=3.13.3.
Is there a fix for CVE-2025-69226?
Yes. aiohttp (PyPI): upgrade to 3.13.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2025-69226?
Check whether you run Aiohttp or aiohttp (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • aiohttp (PyPI): upgrade to 3.13.3 or later
    pip install "aiohttp>=3.13.3"

Affected products

  • Aiohttp
  • aiohttp (PyPI) ECOSYSTEM:introduced=0,fixed=3.13.3

Identifiers

  • CVE-2025-69226
  • GHSA-54jq-c3m8-4m76
  • PYSEC-2026-1097

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.