CVE-2025-69226
Path Disclosure via Static File Normalization in AIOHTTP
Publication date: 2026-01-05
Last updated on: 2026-01-05
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| aiohttp | aiohttp | to 3.13.3 (exc) |
| aiohttp | aiohttp | 3.13.3 |
| aiohttp | aiohttp | From 3.13.2 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
| CWE-200 | The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in AIOHTTP versions 3.13.2 and below, where the path normalization logic for static files intended to prevent path traversal can be bypassed. Specifically, if an application uses the web.static() function (which is not recommended for production), an attacker may be able to determine the existence of absolute path components on the server. This means the attacker can gain information about the file system structure by exploiting how static file paths are handled.
How can this vulnerability impact me? :
The vulnerability allows an attacker to ascertain the existence of absolute path components on the server, potentially revealing sensitive information about the server's file system structure. This information disclosure could aid further attacks or reconnaissance, increasing the risk to the affected system.
What immediate steps should I take to mitigate this vulnerability?
Upgrade AIOHTTP to version 3.13.3 or later, as this version contains the fix for the vulnerability. Additionally, avoid using web.static() in production deployments to reduce exposure.