Skip to main content
VulnerabilityPublished

CVE-2026-128129: AIOHTTP · Unbounded buffering of data received during an upgrade request

Affects lexiconSource GCVE Database

0
Compare
Authoritative record:CVE-2026-128129· High 8.2

Not known to be exploited · CVSS 8.2 High : upgrade to 3.25.2_5 soon.

Data as of 17 Nov 2026, 19:06 UTC

CVSS 4.0 base score
8.2High
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.2
Patch
Available – fixed in 3.25.2_5
CVSS:4.0/AV:N/AC:L/AT:P/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 lexicon to 3.25.2_5.

Affected software

ProductAffectedFixed in
Homebrewlexiconpkg:brew/lexiconOther threatsAffected
  • >=3.25.2_3 <3.25.2_5
Fixed in
  • 3.25.2_5

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade AIOHTTP to version 3.25.2_5 or later, where this vulnerability is fixed. Applying this official patch eliminates the unbounded buffering issue. No additional mitigations are indicated.

Description

AIOHTTP versions >=3.25.2_3 and <3.25.2_5 have a vulnerability where data received during an HTTP upgrade request (such as a WebSocket handshake) is buffered without limit until the handler completes. This can lead to unbounded memory consumption if an attacker streams large amounts of data behind the upgrade request. The issue is fixed in version 3.25.2_5.

References

Community reviews

Loading reviews…