Skip to main content
VulnerabilityPublished

CVE-2026-128131: AIOHTTP · Concatenated compressed streams cause excessive CPU use

Affects gamdlSource GCVE Database

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

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

Data as of 17 Nov 2026, 19:22 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 4.0.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 gamdl to 4.0.0.

Affected software

ProductAffectedFixed in
Homebrewgamdlpkg:brew/gamdlOther threatsAffected
  • >=3.9.1 <4.0.0
Fixed in
  • 4.0.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 issue is fixed in AIOHTTP version 4.0.0. Users should upgrade to version 4.0.0 or later to remediate this vulnerability.

Description

AIOHTTP versions 3.9.1 up to but not including 4.0.0 contain a vulnerability where decompressing concatenated compressed streams (gzip, deflate, or zstd) causes excessive CPU usage due to quadratic time complexity. This can be exploited by an attacker sending specially crafted compressed request bodies or WebSocket messages to block the server's event loop. The issue is fixed in version 4.0.0.

References

Community reviews

Loading reviews…