CVE-2025-69229: AIOHTTP vulnerable to DoS through chunked messages
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.40% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: aio-libs aiohttp 3.13.3.
Low priority for now. Upgrade to aio-libs aiohttp 3.13.3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
AIOHTTP is an asynchronous HTTP client/server framework for asyncio and Python. In versions 3.13.2 and below, handling of chunked messages can result in excessive blocking CPU usage when receiving a large number of chunks. If an application makes use of the request.read() method in an endpoint, it may be possible for an attacker to cause the server to spend a moderate amount of blocking CPU time (e.g. 1 second) while processing the request. This could potentially lead to DoS as the server would be unable to handle other requests during that time. This issue is fixed in version 3.13.3.
- Published
- Jan 6, 2026
- Updated
- Oct 11, 2026
- EPSS
- 0.4% · 34th percentile
- CWE
- CWE-770
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.6
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| aiohttp | aiohttp | cpe:2.3:a:aiohttp:aiohttp |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- aiohttp aiohttpbefore 3.13.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
aio-libs aiohttp
- < 3.13.3affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | python-aiohttp | from 0 | — |
| Debian:13 | python-aiohttp | before 3.11.16-1+deb13u1 | 3.11.16-1+deb13u1 |
| Debian:14 | python-aiohttp | before 3.13.3-1 | 3.13.3-1 |
| openSUSE:Leap 15.6 | python-aiohttp | before 3.9.3-150400.10.36.1 | 3.9.3-150400.10.36.1 |
| openSUSE:Leap 16.0 | python-aiohttp | before 3.11.16-160000.3.1 | 3.11.16-160000.3.1 |
| openSUSE:Leap 16.0 | python-Brotli | before 1.1.0-160000.3.1 | 1.1.0-160000.3.1 |
| openSUSE:Tumbleweed | python-aiohttp | before 3.13.3-1.1 | 3.13.3-1.1 |
| PyPI | aiohttp | before 3.13.3 | 3.13.3 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | python-aiohttp | before 3.6.0-150100.3.32.1 | 3.6.0-150100.3.32.1 |
| SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | python-aiohttp | before 3.9.3-150400.10.36.1 | 3.9.3-150400.10.36.1 |
| SUSE:Linux Enterprise Server 16.0 | python-aiohttp | before 3.11.16-160000.3.1 | 3.11.16-160000.3.1 |
| SUSE:Linux Enterprise Server 16.0 | python-Brotli | before 1.1.0-160000.3.1 | 1.1.0-160000.3.1 |
Same product
aiohttp: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-23334aiohttp.web.static(follow_symlinks=True) is vulnerable to directory traversal53Plan
- CVE-2024-52303aiohttp memory leak when middleware is enabled when requesting a resource with a non-allowed method34Monitor
- CVE-2025-69223AIOHTTP's HTTP Parser auto_decompress feature is vulnerable to zip bomb30Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-69227Jan 6, 2026 · AIOHTTP vulnerable to DoS when bypassing asserts26Monitor
- ← EarlierCVE-2025-69228Jan 6, 2026 · AIOHTTP vulnerable to denial of service through large payloads26Monitor
- Later →CVE-2025-69230Jan 6, 2026 · AIOHTTP Vulnerable to Cookie Parser Warning Storm10Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| aio-libs aiohttp | 3.13.3 · description | Vendor (CNA) |
| debian:python-aiohttp | 3.11.16-1+deb13u1 · Debian:13 | Package registry (OSV) |
| opensuse:python-aiohttp | 3.9.3-150400.10.36.1 · openSUSE:Leap 15.6 | Package registry (OSV) |
| opensuse:python-Brotli | 1.1.0-160000.3.1 · openSUSE:Leap 16.0 | Package registry (OSV) |
| PyPI:aiohttp | 3.13.3 | Package registry (OSV) |
| suse:python-aiohttp | 3.9.3-150400.10.36.1 · SUSE:Linux Enterprise Module for Public Cloud 15 SP4 | Package registry (OSV) |
| suse:python-Brotli | 1.1.0-160000.3.1 · SUSE:Linux Enterprise Server 16.0 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2025-692280 days apartAIOHTTP vulnerable to denial of service through large payloads26Monitor
- CVE-2026-3451685 days apartAIOHTTP: Multipart Header Size Bypass26Monitor
- CVE-2026-54273167 days apartAIOHTTP: HTTP/1 Pipelined Requests Queue Without Limit26Monitor
- CVE-2026-54274167 days apartAIOHTTP: Incomplete websocket frame payloads bypass memory limits26Monitor
- CVE-2026-54277167 days apartAIOHTTP: C HTTP Parser Bypasses max_line_size for Fragmented Lines26Monitor
- CVE-2026-3451385 days apartAIOHTTP: Denial of Service (DoS) via Unbounded DNS Cache in TCPConnector10Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:U/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.