aiohttp: Unread Compressed Request Bodies Bypass client_max_size During Cleanup
Published 15 Jun 2026 · Updated 10 Sept 2026
Is your project on an affected aiohttp?
Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- <3.14.1
- Fixed in
- 3.14.1
pip install 'aiohttp>=3.14.1'Details
Summary
During cleanup it is possible for a compressed request body to be decompressed into memory in one chunk.
Impact
An attacker may be able to send a compressed payload in specific situations that could be decompressed into memory, potentially leading to DoS (a zip bomb edge case).
Workaround
Disable compression if unable to upgrade.
-----
Patch: https://github.com/aio-libs/aiohttp/commit/4f7480e474cccc6a8cc2c92ad3f17a31dedf8232
Is GHSA-g3cq-j2xw-wf74 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected aiohttp, and gives you the command that fixes it.
More advisories for aiohttp
- HighCVE-2026-128124AIOHTTP: Event loop stall in add_domain() wildcard matching · 16 Nov 2026
- MediumCVE-2026-128125AIOHTTP: Unbounded cookie storage in client CookieJar · 16 Nov 2026
- HighCVE-2026-128126AIOHTTP: Too many URL-encoded form fields block the event loop · 16 Nov 2026
- HighCVE-2026-128127AIOHTTP: Base64 multipart parts bypass client_max_size · 16 Nov 2026
- HighCVE-2026-128128AIOHTTP: WebSocket max_msg_size bypass via integer overflow · 16 Nov 2026
- HighCVE-2026-128129AIOHTTP: Unbounded buffering of data received during an upgrade request · 16 Nov 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.