Skip to main content
VulnerabilityPublished

CVE-2026-128132: AIOHTTP · WebSocket receive queue limits bypassed by small or compressed messages

Affects checkovSource GCVE Database

0
Compare
Authoritative record:CVE-2026-128132· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 3.3.30 soon.

Data as of 17 Nov 2026, 18:35 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.08.7
Patch
Available – fixed in 3.3.30
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
Homebrewcheckovpkg:brew/checkovOther threatsAffected
  • >=2.0.615 <3.3.30
Fixed in
  • 3.3.30

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 this vulnerability is fixed. The vendor has provided an official patch addressing the issue. No additional mitigation is required once the patch is applied.

Description

AIOHTTP versions from 2.0.615 up to but not including 3.3.30 have a vulnerability in the WebSocket implementation where the receive queue limits can be bypassed by sending many small or compressed messages. This occurs because empty messages are not counted towards the queue size, and with permessage-deflate compression, a single read can decompress many megabytes of data, causing excessive memory use. The issue allows an attacker to overwhelm the WebSocket server or client memory by sending messages faster than they can be processed. A fix is available in version 3.3.30.

References

Community reviews

Loading reviews…