Skip to main content
VulnerabilityPublished

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

Affects dnsrobocertSource GCVE Database

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

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

Data as of 17 Nov 2026, 19: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.27.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: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 dnsrobocert to 3.27.1_2.

Affected software

ProductAffectedFixed in
Homebrewdnsrobocertpkg:brew/dnsrobocertOther threatsAffected
  • >=3.27.1_1 <3.27.1_2
Fixed in
  • 3.27.1_2

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 3.27.1_2. Users should upgrade to this version or later to remediate the vulnerability. No additional mitigation is required if the patch is applied.

Description

AIOHTTP versions >=3.27.1_1 and <3.27.1_2 have a vulnerability in the WebSocket receive queue handling where small or compressed messages bypass queue limits, causing excessive memory use. This occurs because the WebSocket reader continues parsing frames after the receive queue pauses the transport, and empty messages are not counted towards the queue size. With permessage-deflate compression, a single read can decompress many megabytes of data, potentially exhausting memory.

References

Community reviews

Loading reviews…