CVE-2026-109932: undici WebSocket client vulnerable to Denial of Service via unbounded automatic PONG buffering
Noroxi assessment
Priority: Monitor (action score 30/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.32% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: undici undici 6.29.1, 7.30.1, 8.12.2.
Low priority for now. Upgrade to undici undici 6.29.1, 7.30.1, 8.12.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
undici is an HTTP client library for Node.js. In versions 5.15.0 through 6.29.0, 7.0.0 through 7.30.0, and 8.0.0 through 8.12.1, its WebSocket client, including the bundled WebSocket exposed by Node.js, can be driven to exhaust process memory by a malicious or compromised WebSocket server. For every PING frame received, the client automatically writes a PONG response and ignores the backpressure signal from the socket write, so a server that streams small PING frames while never reading the client's PONGs makes the outbound write queue and heap grow without bound until the Node.js process runs out of memory and terminates. The attack is remote and unauthenticated, needs only a normal WebSocket connection, and is asymmetric, since small inbound PINGs produce a much larger retained outbound queue, with availability the only impact. The issue is fixed in undici 6.29.1, 7.30.1, and 8.12.2, which pause WebSocket frame parsing when the automatic PONG response hits socket backpressure and resume on drain, bounding the outbound queue, and users should upgrade to one of those versions or later. There is no workaround.
- Published
- Oct 15, 2026
- Updated
- Oct 19, 2026
- EPSS
- 0.3% · 24th percentile
- CWE
- CWE-400
Report tools
Action score
30
Monitor
Low priority for now.
- CVSS
- 30 / 40 · 7.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 7.5
- CNA · openjs
- 5.9
- 1.6 point gap
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| nodejs | undici | cpe:2.3:a:nodejs:undici |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- nodejs undici5.15.0 and later · before 6.29.1
- nodejs undici7.0.0 and later · before 7.30.1
- nodejs undici8.0.0 and later · before 8.12.2
Versions reported by the vendor
Affected version ranges reported by the assigning authority (openjs). Independent of NVD's CPE analysis and usually ahead of it.
undici undici
- 6.29.1, 7.30.1, 8.12.2not affected
- 5.15.0 and later · before 6.29.1affected · semver
- 7.0.0 and later · before 7.30.1affected · semver
- 8.0.0 and later · before 8.12.2affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | node-undici | from 0 | — |
| npm | undici | from 5.15.0 · before 6.29.1 | 6.29.1 |
| npm | undici | from 7.0.0 · before 7.30.1 | 7.30.1 |
| npm | undici | from 8.0.0 · before 8.12.2 | 8.12.2 |
| Red Hat:hummingbird:1 | nodejs24 | before 0:24.21.0-1.5.hum1 | 0:24.21.0-1.5.hum1 |
| Red Hat:hummingbird:1 | nodejs24-bin | before 0:24.21.0-1.5.hum1 | 0:24.21.0-1.5.hum1 |
| Red Hat:hummingbird:1 | nodejs24-devel | before 0:24.21.0-1.5.hum1 | 0:24.21.0-1.5.hum1 |
| Red Hat:hummingbird:1 | nodejs24-docs | before 0:24.21.0-1.5.hum1 | 0:24.21.0-1.5.hum1 |
| Red Hat:hummingbird:1 | nodejs24-full-i18n | before 0:24.21.0-1.5.hum1 | 0:24.21.0-1.5.hum1 |
| Red Hat:hummingbird:1 | nodejs24-libs | before 0:24.21.0-1.5.hum1 | 0:24.21.0-1.5.hum1 |
| Red Hat:hummingbird:1 | nodejs24-npm | before 0:11.19.0-1.24.21.0.1.5.hum1 | 0:11.19.0-1.24.21.0.1.5.hum1 |
| Red Hat:hummingbird:1 | nodejs24-npm-bin | before 0:24.21.0-1.5.hum1 | 0:24.21.0-1.5.hum1 |
| Red Hat:hummingbird:1 | nodejs26 | before 0:26.11.1-0.4.hum1 | 0:26.11.1-0.4.hum1 |
| Red Hat:hummingbird:1 | nodejs26-bin | before 0:26.11.1-0.4.hum1 | 0:26.11.1-0.4.hum1 |
| Red Hat:hummingbird:1 | nodejs26-devel | before 0:26.11.1-0.4.hum1 | 0:26.11.1-0.4.hum1 |
| Red Hat:hummingbird:1 | nodejs26-docs | before 0:26.11.1-0.4.hum1 | 0:26.11.1-0.4.hum1 |
| Red Hat:hummingbird:1 | nodejs26-full-i18n | before 0:26.11.1-0.4.hum1 | 0:26.11.1-0.4.hum1 |
| Red Hat:hummingbird:1 | nodejs26-libs | before 0:26.11.1-0.4.hum1 | 0:26.11.1-0.4.hum1 |
| Red Hat:hummingbird:1 | nodejs26-npm | before 0:11.20.0-1.26.11.1.0.4.hum1 | 0:11.20.0-1.26.11.1.0.4.hum1 |
| Red Hat:hummingbird:1 | nodejs26-npm-bin | before 0:26.11.1-0.4.hum1 | 0:26.11.1-0.4.hum1 |
| Red Hat:hummingbird:1 | v8-13.6-devel | before 0:13.6.233.17-1.24.21.0.1.5.hum1 | 0:13.6.233.17-1.24.21.0.1.5.hum1 |
| Red Hat:hummingbird:1 | v8-14.6-devel | before 0:14.6.202.34-1.26.11.1.0.4.hum1 | 0:14.6.202.34-1.26.11.1.0.4.hum1 |
Same product
nodejs: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-35949`undici.request` vulnerable to SSRF using absolute URL on `pathname`40Plan
- CVE-2026-1525undici is vulnerable to Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling')39Monitor
- CVE-2026-109829undici vulnerable to cache poisoning and cross-user disclosure via cross-origin redirects36Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-109869Oct 15, 2026 · undici vulnerable to Denial of Service via unhandled error on excessive content-encodings30Monitor
- ← EarlierCVE-2026-109924Oct 15, 2026 · undici vulnerable to Denial of Service via unbounded memory in the EventSource parser30Monitor
- Later →CVE-2026-87018Oct 15, 2026 · undici vulnerable to Denial of Service via TLS 1.2 certificate-changing renegotiation30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| undici undici | 6.29.1 | Vendor (CNA) |
| undici undici | 7.30.1 | Vendor (CNA) |
| undici undici | 8.12.2 | Vendor (CNA) |
| npm:undici | 6.29.1 | Package registry (OSV) |
| npm:undici | 7.30.1 | Package registry (OSV) |
| npm:undici | 8.12.2 | Package registry (OSV) |
| red hat:nodejs24 | 0:24.21.0-1.5.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs24-bin | 0:24.21.0-1.5.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs24-devel | 0:24.21.0-1.5.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs26 | 0:26.11.1-0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs26-bin | 0:26.11.1-0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs26-devel | 0:26.11.1-0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs26-docs | 0:26.11.1-0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs26-full-i18n | 0:26.11.1-0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs26-libs | 0:26.11.1-0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs26-npm | 0:11.20.0-1.26.11.1.0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:nodejs26-npm-bin | 0:26.11.1-0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:v8-14.6-devel | 0:14.6.202.34-1.26.11.1.0.4.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayOct 28, 2026+12 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- benzdeusreporter
- UlisesGasconremediation developer
- mcollinaremediation reviewer
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-12151120 days apartundici WebSocket client vulnerable to denial of service via fragment count bypass30Monitor
- CVE-2026-9675120 days apartundici WebSocket client vulnerable to denial of service via cumulative fragment bypass30Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-400 · Uncontrolled Resource ConsumptionCVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvd-primary
Root cause
Code that parses nested structures sets no depth or size limit. A small input can turn into a disproportionate processing load.
The bug in code
The whole CWE-400 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
function expand(node) {
return node.children.map(expand);
}Fixed
const MAX_DEPTH = 32;
function expand(node, depth = 0) {
if (depth > MAX_DEPTH) throw new Error("too deep");
return node.children.map((c) => expand(c, depth + 1));
}Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- CVSS5.9 → 7.5
- Severitymedium → high
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (1 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.