Skip to content
Noroxi
CVE-2026-85014· NVD / CVE Program· CNA openjs

undici vulnerable to Denial of Service via WebSocketStream unclean close

undici's experimental WebSocketStream client crashes the whole Node.js process when a remote peer closes the TCP connection without a WebSocket close handshake. On an unclean close the internal socket-close handler calls abort on the writable stream unconditionally and discards the returned promise, but per the WHATWG Streams standard aborting a locked writable returns a promise that rejects with a TypeError. Because the application holds a writer on that writable, which is the only way to write, the rejection is never observed and Node's default unhandled-rejection behavior terminates the process. An untrusted server can therefore crash a client with a single abrupt disconnect, with no authentication and no application mistake. This affects undici versions from 7.0.0 up to 7.29.1 and from 8.0.0 up to 8.10.2. Users should upgrade to undici 7.29.1 or 8.10.2.

HighCVSS 7.5 · v3.1—No exploit Fix available
Published
Sep 4, 2026
Updated
Sep 15, 2026
EPSS
0.4% · 29th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.4%

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.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
nodejsundici

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • nodejs undici7.0.0 and later · before 7.29.1
  • nodejs undici8.0.0 and later · before 8.10.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

    • 7.29.1, 8.10.2not affected
    • 7.0.0 and later · before 7.29.1affected · semver
    • 8.0.0 and later · before 8.10.2affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12node-undiciall versions—
Debian:14node-undicibefore 8.10.2+dfsg+~cs3.2.2-18.10.2+dfsg+~cs3.2.2-1
npmundicifrom 7.0.0 · before 7.29.17.29.1
npmundicifrom 8.0.0 · before 8.10.28.10.2
Red Hat:hummingbird:1grafana12.4before 0:12.4.10-0.2.hum10:12.4.10-0.2.hum1
Red Hat:hummingbird:1nodejs24before 0:24.18.1-0.2.2.hum10:24.18.1-0.2.2.hum1
Red Hat:hummingbird:1nodejs24-binbefore 0:24.18.1-0.2.2.hum10:24.18.1-0.2.2.hum1
Red Hat:hummingbird:1nodejs24-develbefore 0:24.18.1-0.2.2.hum10:24.18.1-0.2.2.hum1
Red Hat:hummingbird:1nodejs24-docsbefore 0:24.18.1-0.2.2.hum10:24.18.1-0.2.2.hum1
Red Hat:hummingbird:1nodejs24-full-i18nbefore 0:24.18.1-0.2.2.hum10:24.18.1-0.2.2.hum1
Red Hat:hummingbird:1nodejs24-libsbefore 0:24.18.1-0.2.2.hum10:24.18.1-0.2.2.hum1
Red Hat:hummingbird:1nodejs24-npmbefore 0:11.16.0-1.24.18.1.0.2.2.hum10:11.16.0-1.24.18.1.0.2.2.hum1
Red Hat:hummingbird:1nodejs24-npm-binbefore 0:24.18.1-0.2.2.hum10:24.18.1-0.2.2.hum1
Red Hat:hummingbird:1nodejs26before 0:26.7.0-1.5.2.hum10:26.7.0-1.5.2.hum1
Red Hat:hummingbird:1nodejs26-binbefore 0:26.7.0-1.5.2.hum10:26.7.0-1.5.2.hum1
Red Hat:hummingbird:1nodejs26-develbefore 0:26.7.0-1.5.2.hum10:26.7.0-1.5.2.hum1
Red Hat:hummingbird:1nodejs26-docsbefore 0:26.7.0-1.5.2.hum10:26.7.0-1.5.2.hum1
Red Hat:hummingbird:1nodejs26-full-i18nbefore 0:26.7.0-1.5.2.hum10:26.7.0-1.5.2.hum1
Red Hat:hummingbird:1nodejs26-libsbefore 0:26.7.0-1.5.2.hum10:26.7.0-1.5.2.hum1
Red Hat:hummingbird:1nodejs26-npmbefore 0:11.19.0-1.26.7.0.1.5.2.hum10:11.19.0-1.26.7.0.1.5.2.hum1
Red Hat:hummingbird:1nodejs26-npm-binbefore 0:26.7.0-1.5.2.hum10:26.7.0-1.5.2.hum1
Red Hat:hummingbird:1v8-14.6-develbefore 0:14.6.202.34-1.26.7.0.1.5.2.hum10:14.6.202.34-1.26.7.0.1.5.2.hum1

Other 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-84961undici vulnerable to TLS certificate validation bypass via dropped connect options in BalancedPool
    36Monitor
  • CVE-2026-13697undici vulnerable to cross-user information disclosure and parse-time crash via degenerate private cache directives
    36Monitor
  • CVE-2026-6734undici vulnerable to cross-origin request routing via SOCKS5 proxy pool reuse
    35Monitor
  • CVE-2026-84933undici vulnerable to cross-user cookie disclosure via Set-Cookie caching in shared caches
    32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
undici undici7.29.1Vendor (CNA)
undici undici8.10.2Vendor (CNA)
debian:node-undici8.10.2+dfsg+~cs3.2.2-1 · Debian:14Package registry (OSV)
npm:undici7.29.1Package registry (OSV)
npm:undici8.10.2Package registry (OSV)
red hat:grafana12.40:12.4.10-0.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs240:24.18.1-0.2.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-bin0:24.18.1-0.2.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-devel0:24.18.1-0.2.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-docs0:24.18.1-0.2.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-full-i18n0:24.18.1-0.2.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-libs0:24.18.1-0.2.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-npm0:11.16.0-1.24.18.1.0.2.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs24-npm-bin0:24.18.1-0.2.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs260:26.7.0-1.5.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-bin0:26.7.0-1.5.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-devel0:26.7.0-1.5.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-docs0:26.7.0-1.5.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-full-i18n0:26.7.0-1.5.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-libs0:26.7.0-1.5.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-npm0:11.19.0-1.26.7.0.1.5.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:nodejs26-npm-bin0:26.7.0-1.5.2.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:v8-14.6-devel0:14.6.202.34-1.26.7.0.1.5.2.hum1 · Red Hat:hummingbird:1Package 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.

No dated events beyond publication.

EPSS, last 120 days

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.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-195340 days apartundici vulnerable to Denial of Service via unrequested WebSocket subprotocol
    30Monitor
  • CVE-2026-1528176 days apartundici is vulnerable to Malicious WebSocket 64-bit length overflows undici parser and crashes the client
    30Monitor
  • CVE-2026-2229176 days apartundici is vulnerable to Unhandled Exception in undici WebSocket Client Due to Invalid server_max_window_bits Validation
    30Monitor
  • CVE-2026-850240 days apartundici vulnerable to Denial of Service via unhandled error in WebSocket permessage-deflate decompression
    23Monitor

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-248 · Uncaught Exception

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records