Is aiohttp 3.14 vulnerable?
PyPI · 6 releases from 3.14.0 to 3.14.5 · latest aiohttp is 3.14.5 · checked 18 Nov 2026
No known advisories in the last release
aiohttp 3.14.5, the last 3.14 release, has no known advisories. 28 advisories affect earlier 3.14.x releases, so update to 3.14.5.
pip install 'aiohttp>=3.14.5'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
Fixed within 3.14.x, affecting earlier releases
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: File descriptor exhaustion in multipart requests
- Affected
- >=2.0.0 <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
Every aiohttp 3.14.x release
Affected: 3.14.0 to 3.14.3. 3.14.4 and later are not affected.
| Version | Known advisories |
|---|---|
| aiohttp 3.14.5 | None |
| aiohttp 3.14.4 | None |
| aiohttp 3.14.3 | CVE-2026-128124, CVE-2026-128125, CVE-2026-128126, CVE-2026-128127, CVE-2026-128128, CVE-2026-128129, CVE-2026-128130, CVE-2026-128131, CVE-2026-128132, CVE-2026-111748, CVE-2026-111749, CVE-2026-111065, CVE-2026-111750, CVE-2026-111066, CVE-2026-111064, CVE-2026-111063, CVE-2026-123817 |
| aiohttp 3.14.2 | CVE-2026-128124, CVE-2026-128125, CVE-2026-128126, CVE-2026-128127, CVE-2026-128128, CVE-2026-128129, CVE-2026-128130, CVE-2026-128131, CVE-2026-128132, CVE-2026-111748, CVE-2026-111749, CVE-2026-111065, CVE-2026-111750, CVE-2026-111066, CVE-2026-111064, CVE-2026-111063, CVE-2026-123817, CVE-2026-69244 |
| aiohttp 3.14.1 | CVE-2026-128124, CVE-2026-128125, CVE-2026-128126, CVE-2026-128127, CVE-2026-128128, CVE-2026-128129, CVE-2026-128130, CVE-2026-128131, CVE-2026-128132, CVE-2026-111748, CVE-2026-111749, CVE-2026-111065, CVE-2026-111750, CVE-2026-111066, CVE-2026-111064, CVE-2026-111063, CVE-2026-123817, CVE-2026-69244, CVE-2026-69243, CVE-2026-59881 |
| aiohttp 3.14.0 | CVE-2026-128124, CVE-2026-128125, CVE-2026-128126, CVE-2026-128127, CVE-2026-128128, CVE-2026-128129, CVE-2026-128130, CVE-2026-128131, CVE-2026-128132, CVE-2026-111748, CVE-2026-111749, CVE-2026-111065, CVE-2026-111750, CVE-2026-111066, CVE-2026-111064, CVE-2026-111063, CVE-2026-123817, CVE-2026-69244, CVE-2026-69243, CVE-2026-59881, CVE-2026-54274, CVE-2026-54275, CVE-2026-54280, CVE-2026-54273, CVE-2026-54278, CVE-2026-54277, CVE-2026-54276, CVE-2026-54279 |
Which of your client projects are still on aiohttp 3.14?
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.