# CVE-2025-69226: aiohttp Path Traversal — Fixed in 3.13.3 🐍 PyPI Not in CISA KEV # CVE-2025-69226 — aiohttp [Fix: aio-libs/aiohttp@f2a86fd](https://github.com/aio-libs/aiohttp/commit/f2a86fd5ac0383000d1715afddfa704413f0711e) CVE-2025-69226 is a Path Traversal vulnerability in aiohttp. A fix is available for aiohttp — see the affected versions and patch details below. AIOHTTP allows for a brute-force leak of internal static filepath components Also known as[GHSA-54jq-c3m8-4m76](/vulnerability/GHSA-54jq-c3m8-4m76)PYSEC-2026-1097 Published Jan 5, 2026 Updated Oct 28, 2026 Affected 1 pkg Patched 1 / 1 Exploits None indexed Exploitation data as of Nov 8, 2026 · OSV.dev, NVD, FIRST.org (EPSS) ## Exploitation Status ### No confirmed exploitation observed yet - CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment. Exploitation and automatability from CISA’s SSVC triage for CVE-2025-69226. ## EPSS Exploitation Probability [via FIRST.org ↗](https://www.first.org/epss/) 0.4%probability of exploitation in next 30 days Lower Risk0.00% Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk 0.00%0.29%0.58%0.87%0.1%0.4%May 26Sep 26Nov 26 Probability of exploitation in the next 30 days, from [FIRST.org EPSS](https://www.first.org/epss/). ## Real-World Exposure 1 pkg affected 🐍`aiohttp` Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems. ## Description 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. ## Affected Packages 1 total 1 fixed Ecosystem Package Vulnerable range Fix 🐍PyPI `aiohttp` all versions 3.13.3`pip install --upgrade 'aiohttp==3.13.3'` ## Affected Products 1 product · 1 configurations Application `aiohttp`aiohttp < 3.13.3 range ## Detection & mitigation playbook Open-source dependency 1. ### Detect Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aiohttp, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version. 2. ### Fix Update aiohttp to 3.13.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-69226 is resolved across your whole dependency graph. 3. ### Workarounds Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves. ## Fixing This On Your OS If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project. Red HatModerate This vulnerability is rated Moderate for Red Hat products. It allows for information disclosure of path components if an application uses aiohttp's web.static() function. Red Hat generally advises against using web.static() for serving static files in production environments, which limits the impact in typical… Workaround published by Red Hat > No mitigation is currently available that meets Red Hat Product Security’s standards for usability, deployment, applicability, or stability. Source: [Red Hat security advisory for CVE-2025-69226](https://access.redhat.com/security/cve/cve-2025-69226) (CC BY 4.0) ## Frequently Asked Questions 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. O3 Security · Impact-Aware SCA ### Is CVE-2025-69226 in your dependencies? Find it across PyPI, including transitive dependencies. [Scan my dependencies](/book-demo) [How O3 SCA works](/impact-aware-sca)