Memory exhaustion via unbounded HTTP trailer accumulation
Published Apr 1, 2026 · Updated Apr 1, 2026
Resource exhaustion in aiohttp before 3.13.4 allows remote attackers to exhaust application memory with crafted HTTP messages. Its HTTP request and response parsers retain attacker-controlled header and trailer fields without enforcing a bounded count. The server path requires direct receipt of a crafted request, while client exposure requires connecting to an attacker-controlled responder.
Summary
What happened
Resource exhaustion in aiohttp before 3.13.4 allows remote attackers to exhaust application memory with crafted HTTP messages. Its HTTP request and response parsers retain attacker-controlled header and trailer fields without enforcing a bounded count. The server path requires direct receipt of a crafted request, while client exposure requires connecting to an attacker-controlled responder.
The record
- CVE
- CVE-2026-22815
- Published
- Apr 1, 2026
- Updated
- Apr 1, 2026
- Vendor
- aio-libs
- Product
- aiohttp
- Classifications
- CWE-770, CWE-400, T1499.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 1, 2026CVE publishedPublication date reported by the CVE source.
- Apr 1, 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.4
What conditions does exploitation require?
What is affected?
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