VulnerabilityPublished 22 Oct 2026Updated 10 Nov 2026

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

Affects apmSource GCVE Database

Compare

Authoritative record:CVE-2026-123817· High 8.7

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

Data as of 10 Nov 2026, 19:02 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.0	8.7

Patch: Available – fixed in 0.34.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

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 10 Nov 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade apm to 0.34.0.

Affected software

Product	Affected	Fixed in
Homebrewapm`pkg:brew/apm`Other threats	Affected >=0.26.0 <0.34.0	Fixed in 0.34.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 in aiohttp version 0.34.0 that fixes this issue by bounding the number of bytes objects kept during frame reassembly. Users should upgrade affected aiohttp versions (>=0.26.0 and <0.34.0) to 0.34.0 or later to remediate this vulnerability.

Description

CVE-2026-123817 is a high-severity vulnerability in aiohttp WebSocket handling where reassembling frames from many small transport reads causes excessive memory and CPU usage. This occurs because the reader keeps one bytes object per read without bounding the count, leading to memory use far beyond the configured max message size. An attacker can exploit this by sending frames segmented into many tiny pieces, causing resource exhaustion on the server or client side. The issue affects aiohttp versions from 0.26.0 up to but not including 0.34.0. A fix is available in version 0.34.0.

Impact

An attacker can cause excessive memory and CPU usage on a WebSocket server or client by sending frames fragmented into many small segments. This can lead to resource exhaustion, potentially degrading service availability or causing denial of service conditions. The vulnerability does not require authentication or user interaction and can be exploited remotely over the network.

Summary

The vulnerability arises during WebSocket frame reassembly in aiohttp when frames arrive fragmented into many small transport reads. The reader accumulates one bytes object per read without limiting the number of such objects, resulting in excessive memory overhead that can far exceed the max_msg_size setting. This can be exploited by an attacker to cause excessive memory and CPU consumption on either the WebSocket server or client by sending frames in numerous tiny segments. The flaw affects aiohttp versions >=0.26.0 and <0.34.0 and is addressed in version 0.34.0. The CVSS 4.0 score is 8.7 (high severity), indicating network attack vector, low complexity, no privileges or user interaction required, and high impact on availability.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 10 Nov 2026, 19:02 UTC

Technical details

References

Community reviews

Related threats