Skip to main content
VulnerabilityPublished

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

Affects pferdSource GCVE Database

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

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

Data as of 17 Nov 2026, 17:50 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.10.0
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 pferd to 3.10.0.

Affected software

ProductAffectedFixed in
Homebrewpferdpkg:brew/pferdOther threatsAffected
  • >=3.4.2 <3.10.0
Fixed in
  • 3.10.0

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 the vulnerability is fixed in AIOHTTP version 3.10.0. Users should upgrade to version 3.10.0 or later to remediate this issue.

Description

AIOHTTP versions from 3.4.2 up to but not including 3.10.0 have a vulnerability in the WebSocket reader where the receive queue limits can be bypassed by small or compressed messages. This occurs because the reader continues parsing frames already received 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…