Skip to main content
VulnerabilityPublished

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

Affects vdirsyncerSource GCVE Database

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

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

Data as of 17 Nov 2026, 17: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 0.21.0_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 vdirsyncer to 0.21.0_2.

Affected software

ProductAffectedFixed in
Homebrewvdirsyncerpkg:brew/vdirsyncerOther threatsAffected
  • >=0.19.0 <0.21.0_2
Fixed in
  • 0.21.0_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 should be applied by upgrading to version 0.21.0_2 or later. This update addresses the receive queue bypass issue and prevents excessive memory use caused by small or compressed WebSocket messages. No additional mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-128132 is a high-severity vulnerability in aiohttp's WebSocket implementation where the receive queue limits can be bypassed by sending many small or compressed messages. This allows an attacker to cause excessive memory consumption by overwhelming the WebSocket server or client with messages faster than they can be processed. The issue arises because empty messages were not counted towards the queue size and compressed frames could decompress into large amounts of data. A patch is available in version 0.21.0_2 to address this flaw.

References

Community reviews

Loading reviews…