Skip to main content
VulnerabilityPublished

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

Affects lue-readerSource GCVE Database

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

Not known to be exploited · CVSS 8.2 High : upgrade to 0.5.0_4 soon.

Data as of 17 Nov 2026, 18:19 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 0.5.0_4
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 lue-reader to 0.5.0_4.

Affected software

ProductAffectedFixed in
Homebrewlue-readerpkg:brew/lue-readerOther threatsAffected
  • >=0.2.0 <0.5.0_4
Fixed in
  • 0.5.0_4

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

AI-suggested

Upgrade to AIOHTTP version 0.5.0_4 or later, where the vulnerability is fixed. Applying this official patch eliminates the unbounded buffering issue. No other mitigations are indicated or required.

Description

AIOHTTP versions from 0.2.0 up to but not including 0.5.0_4 have a vulnerability where data received during an upgrade request (such as a WebSocket handshake) is buffered without limit until the handler finishes. This can lead to unbounded memory consumption if an attacker streams data behind the upgrade request to a handler that does not promptly accept or reject the upgrade. A patch fixing this issue is available in version 0.5.0_4.

References

Community reviews

Loading reviews…