CVE-2026-128128: AIOHTTP · WebSocket max_msg_size bypass via integer overflow
Affects checkovSource GCVE Database
Not known to be exploited · CVSS 7.5 High : upgrade to 3.3.30 soon.
Data as of 17 Nov 2026, 18:38 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 7.5 |
|---|
- Patch
- Available – fixed in 3.3.30
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 13 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 16 Nov 2026.
What to do
Upgrade checkov to 3.3.30.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewcheckovpkg:brew/checkovOther 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
Upgrade AIOHTTP to version 3.3.30 or later, where the integer overflow issue in the max_msg_size check is fixed. If upgrading is not immediately possible, disable the C extension by setting the environment variable AIOHTTP_NO_EXTENSIONS=1 to force usage of the Python reader, which is not affected by this vulnerability.
Description
AIOHTTP's WebSocket implementation contains an integer overflow vulnerability in the max_msg_size check, allowing attackers to bypass message size limits. This occurs because the addition of the declared frame length to the buffered partial message size uses 64-bit arithmetic, which can overflow for lengths near 2^63. Exploiting this flaw enables an attacker to send an oversized WebSocket message that causes unbounded memory consumption. A fix is available in version 3.3.30. Users unable to upgrade can mitigate the issue by disabling C extensions using the Python reader with the environment variable AIOHTTP_NO_EXTENSIONS=1.
References
- github.com/aio-libs/aiohttp/security/advisories/GHSA-3rp8-rxj8-mvjw (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-128128 (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13415 (opens in a new tab)
- github.com/aio-libs/aiohttp/pull/13494 (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/8c8906a19f64e52ef6a7d44d65217eb3c5af413f (opens in a new tab)
- github.com/aio-libs/aiohttp/commit/8cfbe9abe5e11b84006a10f9bdf82bf607671dab (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)