CVE-2026-123817: Aiohttp · Prior to 3.14.4, the WebSocket reader retains one bytes object for each transport read
Affects aiohttpSource GCVE Database
Not known to be exploited · CVSS 8.7 High : upgrade to 3.14.4 soon.
Data as of 19 Nov 2026, 12:39 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 8.7 |
|---|
- Patch
- Available – fixed in 3.14.4
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade aiohttp to 3.14.4.
Patches and advisories
- github.com/aio-libs/aiohttp/commit/09bcaa73ff084a0c539bbf16a0a78743acb7141f (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/6a4f6682817839313b04b8e5cea2b39c1a88ab4f (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13352 (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13612 (opens in a new tab)
- github.com/aio-libs/aiohttp/security/advisories/GHSA-2g87-pp6c-29x5 (opens in a new tab)
Affected software
| Product | Affected | Fixed in |
|---|---|---|
PyPIaiohttppkg:pypi/aiohttpOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in aiohttp version 3.14.4. Users and administrators should upgrade to version 3.14.4 or later to remediate this vulnerability. No other mitigation is required as the issue is resolved in the official patch.
Description
A vulnerability in aiohttp prior to version 3.14.4 allows a malicious peer to cause excessive memory consumption or denial of service by splitting a WebSocket frame into many tiny reads. This causes the WebSocket reader to retain one bytes object per transport read, leading to high memory overhead. The issue affects both servers receiving frames from malicious clients and clients receiving frames from malicious servers. The flaw is fixed in version 3.14.4.
References
- github.com/aio-libs/aiohttp/releases/tag/v3.14.4 (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/09bcaa73ff084a0c539bbf16a0a78743acb7141f (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/6a4f6682817839313b04b8e5cea2b39c1a88ab4f (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13352 (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13612 (opens in a new tab)
- github.com/aio-libs/aiohttp/security/advisories/GHSA-2g87-pp6c-29x5 (opens in a new tab)