CVE-2025-69229: AIOHTTP vulnerable to DoS through chunked messages

Published Jan 5, 2026
·
Updated

Summary

Handling of chunked messages can result in excessive blocking CPU usage when receiving a large number of chunks.

Impact

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.

-----

Patch: https://github.com/aio-libs/aiohttp/commit/dc3170b56904bdf814228fae70a5501a42a6c712 Patch: https://github.com/aio-libs/aiohttp/commit/4ed97a4e46eaf61bd0f05063245f613469700229

Other sources

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.

MITRE

Affected Software

3 affected componentsFixes available
pip/aiohttp<=3.13.2
3.13.3
aiohttp aiohttp<3.13.3
IBM Concert Software<=1.0.0-2.2.0

Event History

Jan 5, 2026
Advisory Published
via GitHub·11:13 PM
Data Sourced
via GitHub·11:13 PM
DescriptionWeaknessAffected Software
CVE Published
via MITRE·11:37 PM
Data Sourced
via MITRE·11:37 PM
DescriptionWeakness
Jan 6, 2026
Data Sourced
via NVD·12:15 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·12:15 AM
RemedyAffected Software
Apr 6, 2026
Data Sourced
via IBM·12:00 AM
DescriptionAffected Software

Parent advisories

This vulnerability appears in the following advisories.

Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2025-69229?

CVE-2025-69229 is considered a moderate severity vulnerability due to its potential to cause excessive CPU usage.

2

How do I fix CVE-2025-69229?

To fix CVE-2025-69229, upgrade the aiohttp package to version 3.13.3 or above.

3

What causes the issue in CVE-2025-69229?

CVE-2025-69229 arises from improper handling of chunked messages, leading to blocking CPU usage in affected applications.

4

Who is affected by CVE-2025-69229?

CVE-2025-69229 affects applications that utilize the request.read() method in conjunction with aiohttp versions prior to 3.13.3.

5

What symptoms indicate an exploitation of CVE-2025-69229?

Indicators of exploitation for CVE-2025-69229 may include unusually high CPU usage on the server when handling chunked requests.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203