Memory exhaustion via per-field multipart size reset
Published Jan 5, 2026 · Updated Jan 5, 2026
Resource exhaustion in aiohttp before 3.13.3 allows remote attackers to freeze servers via multipart requests handled by Request.post(). The Request.post() multipart loop resets its size counter for every field, so each part can remain below client_max_size while the combined form grows without limit. Exploitation requires an application handler that calls Request.post(); a crafted multi-field upload then exhausts process memory and interrupts the service.
Summary
What happened
Resource exhaustion in aiohttp before 3.13.3 allows remote attackers to freeze servers via multipart requests handled by Request.post(). The Request.post() multipart loop resets its size counter for every field, so each part can remain below client_max_size while the combined form grows without limit. Exploitation requires an application handler that calls Request.post(); a crafted multi-field upload then exhausts process memory and interrupts the service.
The record
- CVE
- CVE-2025-69228
- Published
- Jan 5, 2026
- Updated
- Jan 5, 2026
- Vendor
- aio-libs
- Product
- aiohttp
- Classifications
- CWE-770, T1499.003
- 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