CVE-2025-69226: AIOHTTP vulnerable to brute-force leak of internal static file path components
Summary Path normalization for static files prevents path traversal, but opens up the ability for an attacker to ascertain the existence of absolute path components. Impact 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.
Published Jan 5, 2026 · Updated Jan 6, 2026
Affected packages
aiohttp
- Ecosystem
- PyPI
- Affected
- <= 3.13.2
- Fixed in
- 3.13.3
- Check
pip show aiohttp
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Path normalization for static files prevents path traversal, but opens up the ability for an attacker to ascertain the existence of absolute path components.
Impact
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.
------
Patch: https://github.com/aio-libs/aiohttp/commit/f2a86fd5ac0383000d1715afddfa704413f0711e
Credited to ThomasRinsma, Dreamsorcerer, bdraco.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-128124
AIOHTTP: Event loop stall in add_domain() wildcard matching
high8.2Nov 16, 2026CVE-2026-128125
AIOHTTP: Unbounded cookie storage in client CookieJar
medium6.3Nov 16, 2026CVE-2026-128126
AIOHTTP: Too many URL-encoded form fields block the event loop
high8.7Nov 16, 2026CVE-2026-128127
AIOHTTP: Base64 multipart parts bypass client_max_size
high7.5Nov 16, 2026CVE-2026-128128
AIOHTTP: WebSocket max_msg_size bypass via integer overflow
high7.5Nov 16, 2026CVE-2026-128129
AIOHTTP: Unbounded buffering of data received during an upgrade request
high8.2Nov 16, 2026
