Path-component disclosure via unnormalized static route matching
Published Jan 5, 2026 · Updated Jan 5, 2026
Information disclosure in aio-libs aiohttp before 3.13.3 allows remote attackers to infer server path components via static-file requests. StaticResource.resolve matches the raw request path against its route prefix before normalization, so traversal segments reach existence-dependent handling outside the static root. Exposure requires an application to publish a reachable web.static() route; the oracle reveals path-component existence but does not read file contents.
Summary
What happened
Information disclosure in aio-libs aiohttp before 3.13.3 allows remote attackers to infer server path components via static-file requests. StaticResource.resolve matches the raw request path against its route prefix before normalization, so traversal segments reach existence-dependent handling outside the static root. Exposure requires an application to publish a reachable web.static() route; the oracle reveals path-component existence but does not read file contents.
The record
- CVE
- CVE-2025-69226
- Published
- Jan 5, 2026
- Updated
- Jan 5, 2026
- Vendor
- aio-libs
- Product
- aiohttp
- Classifications
- CWE-22, CWE-200, T1083
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 5, 2026CVE publishedPublication date reported by the CVE source.
- Jan 5, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 3.13.3
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo