Skip to main content
VulnerabilityPublished

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

Affects knot-resolverSource GCVE Database

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

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

Data as of 17 Nov 2026, 19:03 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 6.5.0_1
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 knot-resolver to 6.5.0_1.

Affected software

ProductAffectedFixed in
Homebrewknot-resolverpkg:brew/knot-resolverOther threatsAffected
  • >=6.1.0 <6.5.0_1
Fixed in
  • 6.5.0_1

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 6.5.0_1. Users should upgrade to this version or later to remediate the vulnerability. No additional mitigation steps are required beyond applying the official patch.

Description

AIOHTTP's WebSocket implementation has a vulnerability where the receive queue limits can be bypassed by sending many small or compressed messages. This occurs because the WebSocket reader continues parsing frames after the receive queue has paused the transport, and empty messages are not counted towards the queue size. When permessage-deflate compression is used, a single read of compressed frames can add many megabytes of decompressed messages to the queue. This can lead to excessive memory consumption on the server or client side.

References

Community reviews

Loading reviews…