Skip to main content
VulnerabilityPublished Updated

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

Affects aiderSource GCVE Database

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

Not known to be exploited · CVSS 8.7 High.

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.
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

Affected software

ProductAffectedFixed in
Homebrewaiderpkg:brew/aiderOther threatsAffected
  • >=0.47.1
Fixed in–

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

AI-suggested

Until a fix is available, consider limiting the size and rate of WebSocket frames accepted or deploying network-level protections to mitigate potential resource exhaustion attacks.

Description

CVE-2026-123817 is a high-severity vulnerability in the aiohttp WebSocket implementation where reassembling frames delivered in many small segments causes excessive memory and CPU usage. This occurs because the reader retains one bytes object per small read without bounding the count, leading to memory consumption far exceeding the configured max message size. Both WebSocket servers and clients can be affected by an attacker or malicious server sending frames in numerous tiny segments.

References

Community reviews

Loading reviews…