CVE-2026-12151

undici WebSocket client vulnerable to denial of service via fragment count bypass

HIGH
7.5
CVSS Score
Published: June 17, 2026 at 04:05 PM UTC
Updated: September 11, 2026 at 01:50 PM UTC
7 products affected across 3 vendorsUndiciOpenShift AIHardened Images

Using undici by undici?

Get instant alerts when new vulnerabilities affect undici - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.5
Exploit prediction
EPSS 0.8%
SSVC
No known exploit

Description

Impact: The undici WebSocket client enforces maxPayloadSize on the cumulative byte count of fragments in a message but does not enforce a limit on the number of fragments. A malicious WebSocket server can stream many small or empty continuation frames that each pass per-frame and cumulative-size validation, collectively causing unbounded memory growth in the client process. The result is memory exhaustion and a denial of service. Affected applications are those using the undici WebSocket client (new WebSocket(...)) or the WebSocketStream API that can be induced to connect to an attacker-controlled or compromised WebSocket endpoint. All releases starting at undici 6.17.0 are affected. Patches: Upgrade to undici >= 6.26.0, >= 7.28.0, or >= 8.5.0. Workarounds: No workaround is available. The fix must be applied through an upgrade.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.17.0 ≤ v < 6.27.07.0.0 ≤ v < 7.28.08.0.0 ≤ v < 8.5.0
Affected range stops below 6.27.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 7.28.0, so it looks safe — our inference, not a vendor statement
Affected range stops below 8.5.0, so it looks safe — our inference, not a vendor statement
All versions
Vendor states this is fixed in 24.18.0-0.3.hum1 (unaffected)
Vendor states this is fixed in 26.5.0-1.3.hum1 (unaffected)
All versions
Vendor states this is fixed in 1787121387 (unaffected)
Vendor states this is fixed in 1787801527 (unaffected)
v < 6.26.07.0.0 ≤ v < 7.28.08.0.0 ≤ v < 8.5.07.0.08.0.0
Vendor states this is fixed in 6.26.0 (unaffected)
Vendor states this is fixed in 7.28.0 (unaffected)
Vendor states this is fixed in 8.5.0 (unaffected)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (31)

Vendor Advisory
Source: cverecord
https://cna.openjsf.org/security-advisories.html
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/security/cve/CVE-2026-12151
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://bugzilla.redhat.com/show_bug.cgi?id=2489980
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:34342
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:35841
Source: 0b0ca135-0b70-47e7-9f44-1890c2a1c46c
https://access.redhat.com/errata/RHSA-2026:35842

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.5HIGHopenjs
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-400CWE-770

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card