CVE-2026-123817: aiohttp · Multiple instances of excessive or unbounded memory/CPU use
Affects bztSource GCVE Database
Not known to be exploited · CVSS 8.7 High : upgrade to 1.17.1_2 soon.
Data as of 19 Nov 2026, 20:25 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 4.0 | 8.7 |
|---|
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 1.17.1_2
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 19 Nov 2026.
What to do
Upgrade bzt to 1.17.1_2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewbztpkg:brew/bztOther 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 patch is available and has been released in aiohttp version 1.17.1_2. Users should upgrade to this version or later to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.
Description
CVE-2026-123817 is a vulnerability in aiohttp's WebSocket frame reassembly process where multiple small transport reads cause excessive memory usage. The reader retains one bytes object per read without bounding the count, leading to memory consumption far exceeding the configured max_msg_size. This can be exploited by sending a frame in many tiny segments to cause excessive memory use on the server or client side.
References
- github.com/aio-libs/aiohttp/security/advisories/GHSA-2g87-pp6c-29x5 (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/09bcaa73ff084a0c539bbf16a0a78743acb7141f (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/0ae507423f681161efa77d20052b4054397c7fb6 (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/3d850ee9b92573c7e913821cbcb96005beb3f4df (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/47babd8c23ca79e2bae6cc8dcb5752b61e369fc7 (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/615fec3d4f088f30d2ee72cad760152e92aa1c53 (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/6963ee0befec1502b6bb7b4db6c72d044c08f4fa (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/6a4f6682817839313b04b8e5cea2b39c1a88ab4f (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/8cfbe9abe5e11b84006a10f9bdf82bf607671dab (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/a555ab698e08e9baea7386d5b4c0761cb8956fdd (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/c6ac0e44c3c573ff9616f4a6a532992538b31e43 (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/d925a80539ffd227da1d93ab4a5bff123cc777db (opens in a new tab)
- github.com/aio-libs/aiohttp (opens in a new tab)
- github.com/aio-libs/aiohttp/releases/tag/v3.14.4 (opens in a new tab)