Is aiohttp 0.3 vulnerable?
PyPI · 1 release from 0.3.0 to 0.3.0 · latest aiohttp is 3.14.5 · checked 18 Nov 2026
Yes: 60 known advisories
Yes. aiohttp 0.3.0, the last 0.3 release, is affected by 60 known security advisories (13 high, 29 medium, 18 low), including CVE-2026-128124, CVE-2026-128126, CVE-2026-128127. Upgrade to 3.14.4 or later to fix all of them.
pip install 'aiohttp>=3.14.4'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
Advisories affecting aiohttp 0.3.0
AIOHTTP: Event loop stall in add_domain() wildcard matching
- Affected
- <3.14.4
- Fixed in
- 3.14.4
AIOHTTP: Unbounded cookie storage in client CookieJar
- Affected
- <3.14.4
- Fixed in
- 3.14.4
AIOHTTP: Too many URL-encoded form fields block the event loop
- Affected
- <3.14.4
- Fixed in
- 3.14.4
AIOHTTP: Base64 multipart parts bypass client_max_size
- Affected
- <3.14.4
- Fixed in
- 3.14.4
AIOHTTP: WebSocket max_msg_size bypass via integer overflow
- Affected
- <3.14.4
- Fixed in
- 3.14.4
AIOHTTP: Unbounded buffering of data received during an upgrade request
- Affected
- <3.14.4
- Fixed in
- 3.14.4
AIOHTTP: Pure-Python parser request replay and buffer growth behind a declined upgrade
- Affected
- <3.14.4
- Fixed in
- 3.14.4
AIOHTTP: Concatenated compressed streams cause excessive CPU use
- Affected
- <3.14.4
- Fixed in
- 3.14.4
AIOHTTP: WebSocket receive queue limits bypassed by small or compressed messages
- Affected
- <3.14.4
- Fixed in
- 3.14.4
AIOHTTP: Absolute-form request targets can spoof Request.scheme
- Affected
- <3.14.4
- Fixed in
- 3.14.4
AIOHTTP: Cookie from subdomain can remove Host-Only Scope from existing cookies
- Affected
- <3.14.4
- Fixed in
- 3.14.4
AIOHTTP: Connector pool exhaustion via Max-Age overflow
- Affected
- <3.14.4
- Fixed in
- 3.14.4
AIOHTTP: Pure-Python parser request smuggling
- Affected
- <3.14.4
- Fixed in
- 3.14.4
aiohttp server lacks an initial request/header timeout
- Affected
- <3.14.4
- Fixed in
- 3.14.4
AIOHTTP: Secure attribute not enforced for shared cookie
- Affected
- <3.14.4
- Fixed in
- 3.14.4
aiohttp: Multiple instances of excessive or unbounded memory/CPU use
- Affected
- <3.14.4
- Fixed in
- 3.14.4
AIOHTTP: Out-of-bounds heap read in C HTTP response parser error path (malformed chunked response)
- Affected
- <3.14.3
- Fixed in
- 3.14.3
AIOHTTP: HTTP request smuggling via WebSocket upgrade
- Affected
- <3.14.2
- Fixed in
- 3.14.2
AIOHTTP: WebSocket client accepts compressed frames without negotiated permessage-deflate
- Affected
- <3.14.2
- Fixed in
- 3.14.2
aiohttp: Incomplete websocket frame payloads bypass memory limits
- Affected
- <3.14.1
- Fixed in
- 3.14.1
aiohttp: TLS Server Hostname Override Is Ignored When Reusing HTTPS Connections
- Affected
- <3.14.1
- Fixed in
- 3.14.1
aiohttp: Payload Response Resources Are Not Closed After Mid-Body Disconnect
- Affected
- <3.14.1
- Fixed in
- 3.14.1
aiohttp: HTTP/1 Pipelined Requests Queue Without Limit
- Affected
- <3.14.1
- Fixed in
- 3.14.1
aiohttp: Unread Compressed Request Bodies Bypass client_max_size During Cleanup
- Affected
- <3.14.1
- Fixed in
- 3.14.1
aiohttp: C HTTP Parser Bypasses max_line_size for Fragmented Lines
- Affected
- <3.14.1
- Fixed in
- 3.14.1
aiohttp: DigestAuthMiddleware Applies Credentials to Cross-Origin Redirect Challenges
- Affected
- <3.14.1
- Fixed in
- 3.14.1
aiohttp: Host-Only Cookies Become Domain Cookies After CookieJar Persistence
- Affected
- <3.14.1
- Fixed in
- 3.14.1
aiohttp: CRLF injection in multipart headers
- Affected
- <3.14.0
- Fixed in
- 3.14.0
AIOHTTP is vulnerable to cross-origin redirect with per-request cookies
- Affected
- <3.14.0
- Fixed in
- 3.14.0
AIOHTTP is Vulnerable to Deserialization of Untrusted Data
- Affected
- <3.14.0
- Fixed in
- 3.14.0
AIOHTTP accepts duplicate Host headers
- Affected
- <3.13.4
- Fixed in
- 3.13.4
AIOHTTP's C parser (llhttp) accepts null bytes and control characters in response header values - header injection/security bypass
- Affected
- <3.13.4
- Fixed in
- 3.13.4
AIOHTTP has HTTP response splitting via \r in reason phrase
- Affected
- <3.13.4
- Fixed in
- 3.13.4
AIOHTTP leaks Cookie and Proxy-Authorization headers on cross-origin redirect
- Affected
- <3.13.4
- Fixed in
- 3.13.4
AIOHTTP has late size enforcement for non-file multipart fields causes memory DoS
- Affected
- <3.13.4
- Fixed in
- 3.13.4
AIOHTTP has a Multipart Header Size Bypass
- Affected
- <3.13.4
- Fixed in
- 3.13.4
AIOHTTP affected by UNC SSRF/NTLMv2 Credential Theft/Local File Read in static resource handler on Windows
- Affected
- <3.13.4
- Fixed in
- 3.13.4
AIOHTTP has CRLF injection through multipart part content type header construction
- Affected
- <3.13.4
- Fixed in
- 3.13.4
AIOHTTP Affected by Denial of Service (DoS) via Unbounded DNS Cache in TCPConnector
- Affected
- <3.13.4
- Fixed in
- 3.13.4
aiohttp allows unlimited trailer headers, leading to possible uncapped memory usage
- Affected
- <3.13.4
- Fixed in
- 3.13.4
AIOHTTP Vulnerable to Cookie Parser Warning Storm
- Affected
- <3.13.3
- Fixed in
- 3.13.3
AIOHTTP vulnerable to DoS through chunked messages
- Affected
- <3.13.3
- Fixed in
- 3.13.3
AIOHTTP vulnerable to denial of service through large payloads
- Affected
- <3.13.3
- Fixed in
- 3.13.3
AIOHTTP vulnerable to DoS when bypassing asserts
- Affected
- <3.13.3
- Fixed in
- 3.13.3
AIOHTTP vulnerable to brute-force leak of internal static file path components
- Affected
- <3.13.3
- Fixed in
- 3.13.3
AIOHTTP has unicode match groups in regexes for ASCII protocol elements
- Affected
- <3.13.3
- Fixed in
- 3.13.3
AIOHTTP's unicode processing of header values could cause parsing discrepancies
- Affected
- <3.13.3
- Fixed in
- 3.13.3
AIOHTTP's HTTP Parser auto_decompress feature is vulnerable to zip bomb
- Affected
- <3.13.3
- Fixed in
- 3.13.3
AIOHTTP is vulnerable to HTTP Request/Response Smuggling through incorrect parsing of chunked trailer sections
- Affected
- <3.12.14
- Fixed in
- 3.12.14
aiohttp allows request smuggling due to incorrect parsing of chunk extensions
- Affected
- <3.10.11
- Fixed in
- 3.10.11
aiohttp vulnerable to Denial of Service when trying to parse malformed POST requests
- Affected
- <3.9.4
- Fixed in
- 3.9.4
aiohttp Cross-site Scripting vulnerability on index pages for static file handling
- Affected
- <3.9.4
- Fixed in
- 3.9.4
aiohttp's HTTP parser (the python one, not llhttp) still overly lenient about separators
- Affected
- <3.9.2
- Fixed in
- 3.9.2
aiohttp's ClientSession is vulnerable to CRLF injection via version
- Affected
- <3.9.0
- Fixed in
- 3.9.0
aiohttp's ClientSession is vulnerable to CRLF injection via method
- Affected
- <3.9.0
- Fixed in
- 3.9.0
aiohttp has vulnerable dependency that is vulnerable to request smuggling
- Affected
- <3.8.6
- Fixed in
- 3.8.6
AIOHTTP has problems in HTTP parser (the python one, not llhttp)
- Affected
- <3.8.6
- Fixed in
- 3.8.6
Aiohttp has inconsistent interpretation of `Content-Length` vs. `Transfer-Encoding` differing in C and Python fallbacks
- Affected
- <3.8.0
- Fixed in
- 3.8.0
aiohttp.web.Application vulnerable to HTTP request smuggling via llhttp HTTP request parser
- Affected
- <3.8.5
- Fixed in
- 3.8.5
`aiohttp` Open Redirect vulnerability (`normalize_path_middleware` middleware)
- Affected
- <3.7.4
- Fixed in
- 3.7.4
Which of your client projects are still on aiohttp 0.3?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact aiohttp version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other aiohttp versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.