aiohttp.web.Application vulnerable to HTTP request smuggling via llhttp HTTP request parser
Published 20 Jul 2023 · 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.8.5
- Fixed in
- 3.8.5
pip install 'aiohttp>=3.8.5'Details
Impact
aiohttp v3.8.4 and earlier are bundled with llhttp v6.0.6 which is vulnerable to CVE-2023-30589. The vulnerable code is used by aiohttp for its HTTP request parser when available which is the default case when installing from a wheel.
This vulnerability only affects users of aiohttp as an HTTP server (ie aiohttp.Application), you are not affected by this vulnerability if you are using aiohttp as an HTTP client library (ie aiohttp.ClientSession).
Reproducer
from aiohttp import web
async def example(request: web.Request):
headers = dict(request.headers)
body = await request.content.read()
return web.Response(text=f"headers: {headers} body: {body}")
app = web.Application()
app.add_routes([web.post('/', example)])
web.run_app(app)Sending a crafted HTTP request will cause the server to misinterpret one of the HTTP header values leading to HTTP request smuggling.
$ printf "POST / HTTP/1.1\r\nHost: localhost:8080\r\nX-Abc: \rxTransfer-Encoding: chunked\r\n\r\n1\r\nA\r\n0\r\n\r\n" \
| nc localhost 8080
Expected output:
headers: {'Host': 'localhost:8080', 'X-Abc': '\rxTransfer-Encoding: chunked'} body: b''
Actual output (note that 'Transfer-Encoding: chunked' is an HTTP header now and body is treated differently)
headers: {'Host': 'localhost:8080', 'X-Abc': '', 'Transfer-Encoding': 'chunked'} body: b'A'Patches
Upgrade to the latest version of aiohttp to resolve this vulnerability. It has been fixed in v3.8.5: `pip install aiohttp >= 3.8.5`
Workarounds
If you aren't able to upgrade you can reinstall aiohttp using AIOHTTP_NO_EXTENSIONS=1 as an environment variable to disable the llhttp HTTP request parser implementation. The pure Python implementation isn't vulnerable to request smuggling:
$ python -m pip uninstall --yes aiohttp $ AIOHTTP_NO_EXTENSIONS=1 python -m pip install --no-binary=aiohttp --no-cache aiohttp
References
- https://nvd.nist.gov/vuln/detail/CVE-2023-30589
- https://hackerone.com/reports/2001873
Is GHSA-45c4-8wx5-qw6w 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
- Linkgithub.com/aio-libs/aiohttp/security/advisories/GHSA-45c4-8wx5-qw6w
- Advisorynvd.nist.gov/vuln/detail/CVE-2023-37276
- Linkgithub.com/aio-libs/aiohttp/commit/9337fb3f2ab2b5f38d7e98a194bde6f7e3d16c40
- Linkgithub.com/aio-libs/aiohttp/commit/9c13a52c21c23dfdb49ed89418d28a5b116d0681
- Linkhackerone.com/reports/2001873
- Packagegithub.com/aio-libs/aiohttp
- Linkgithub.com/aio-libs/aiohttp/blob/v3.8.4/.gitmodules
- Linkgithub.com/pypa/advisory-database/tree/main/vulns/aiohttp/PYSEC-2023-120.yaml
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.