CVE-2024-23829: aiohttp's HTTP parser (the python one, not llhttp) still overly lenient about separators
Summary Security-sensitive parts of the Python HTTP parser retained minor differences in allowable character sets, that must trigger error handling to robustly match frame boundaries of proxies in order to protect against injection of additional requests. Additionally, validation could trigger exceptions that were not handled consistently with processing of other malformed input.
Published Jan 29, 2024 · Updated Nov 3, 2025
Affected packages
aiohttp
- Ecosystem
- PyPI
- Affected
- < 3.9.2
- Fixed in
- 3.9.2
- Check
pip show aiohttp
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Security-sensitive parts of the *Python HTTP parser* retained minor differences in allowable character sets, that must trigger error handling to robustly match frame boundaries of proxies in order to protect against injection of additional requests. Additionally, validation could trigger exceptions that were not handled consistently with processing of other malformed input.
Details
These problems are rooted in pattern matching protocol elements, previously improved by PR #3235 and GHSA-gfw2-4jvh-wgfg:
- The expression
HTTP/(\d).(\d)lacked another backslash to clarify that the separator should be a literal dot, not just *any* Unicode code point (result:HTTP/(\d)\.(\d)).
- The HTTP version was permitting Unicode digits, where only ASCII digits are standards-compliant.
- Distinct regular expressions for validating HTTP Method and Header field names were used - though both should (at least) apply the common restrictions of rfc9110
token.
PoC
GET / HTTP/1ö1 GET / HTTP/1.𝟙 GET/: HTTP/1.1 Content-Encoding?: chunked
Impact
Primarily concerns running an aiohttp server without llhttp:
- behind a proxy: Being more lenient than internet standards require could, depending on deployment environment, assist in request smuggling.
- directly accessible or exposed behind proxies relaying malformed input: the unhandled exception could cause excessive resource consumption on the application server and/or its logging facilities.
-----
Patch: https://github.com/aio-libs/aiohttp/pull/8074/files
Credited to pajod.
References
- https://github.com/aio-libs/aiohttp/security/advisories/GHSA-8qpw-xqxj-h4r2
- https://github.com/aio-libs/aiohttp/security/advisories/GHSA-gfw2-4jvh-wgfg
- https://github.com/aio-libs/aiohttp/pull/3235
- https://github.com/aio-libs/aiohttp/pull/8074/files
- https://github.com/aio-libs/aiohttp/commit/33ccdfb0a12690af5bb49bda2319ec0907fa7827
- https://nvd.nist.gov/vuln/detail/CVE-2024-23829
- https://github.com/aio-libs/aiohttp/pull/8074
- https://github.com/pypa/advisory-database/tree/main/vulns/aiohttp/PYSEC-2024-26.yaml
- https://lists.fedoraproject.org/archives/list/[email protected]/message/ICUOCFGTB25WUT336BZ4UNYLSZOUVKBD
- https://lists.fedoraproject.org/archives/list/[email protected]/message/XXWVZIVAYWEBHNRIILZVB3R3SDQNNAA7
- https://lists.debian.org/debian-lts-announce/2025/02/msg00002.html
- https://github.com/advisories/GHSA-8qpw-xqxj-h4r2
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More PyPI vulnerabilities
All PyPI entriesCVE-2026-128124
AIOHTTP: Event loop stall in add_domain() wildcard matching
high8.2Nov 16, 2026CVE-2026-128125
AIOHTTP: Unbounded cookie storage in client CookieJar
medium6.3Nov 16, 2026CVE-2026-128126
AIOHTTP: Too many URL-encoded form fields block the event loop
high8.7Nov 16, 2026CVE-2026-128127
AIOHTTP: Base64 multipart parts bypass client_max_size
high7.5Nov 16, 2026CVE-2026-128128
AIOHTTP: WebSocket max_msg_size bypass via integer overflow
high7.5Nov 16, 2026CVE-2026-128129
AIOHTTP: Unbounded buffering of data received during an upgrade request
high8.2Nov 16, 2026
