Skip to main content
VulnerabilityPublished Updated

CVE-2026-123817: aiohttp · Multiple instances of excessive or unbounded memory/CPU use

Affects lue-readerSource GCVE Database

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

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

Data as of 19 Nov 2026, 20:25 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
EPSS
0.3% chance of exploitation in 30 days – higher than 32% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 0.5.0_4
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 9 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 19 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

A fix is available in aiohttp version 0.5.0_4. Users should upgrade to this version or later to remediate the vulnerability. No additional mitigation steps are indicated by the vendor advisory.

Description

CVE-2026-123817 is a vulnerability in the aiohttp WebSocket frame reassembly process where the reader keeps one bytes object per small transport read without bounding the count. This can cause excessive memory and CPU usage when frames arrive in many tiny segments. An attacker can exploit this by sending a frame fragmented into numerous small pieces, leading to resource exhaustion on the server or client. The issue affects versions >=0.2.0 and <0.5.0_4 and is fixed in version 0.5.0_4.

References

Community reviews

Loading reviews…