Skip to main content
VulnerabilityPublished

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

Affects dnstwistSource GCVE Database

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

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

Data as of 17 Nov 2026, 19:37 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 20250130_14
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 dnstwist to 20250130_14.

Affected software

ProductAffectedFixed in
Homebrewdnstwistpkg:brew/dnstwistOther threatsAffected
  • >=20220815 <20250130_14
Fixed in
  • 20250130_14

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 should be applied. The issue is fixed in AIOHTTP version 20250130_14. Users should upgrade to this version or later to mitigate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

A vulnerability in AIOHTTP's WebSocket implementation allows attackers to bypass receive queue limits by sending many small or compressed messages. This can cause excessive memory consumption on the server or client side. The issue arises because the WebSocket reader continues parsing frames after the receive queue pauses the transport, and empty messages are not counted towards the queue size. A fix is available in version 20250130_14.

References

Community reviews

Loading reviews…