Detection of Error Condition Without Action Affecting nodejs26 package, versions *


Severity

Recommended
0.0
medium
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.35% (29th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL10-NODEJS26-19536080
  • published5 Sept 2026
  • disclosed4 Sept 2026

Introduced: 4 Sep 2026

NewCVE-2026-85014  (opens in a new tab)
CWE-390  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:10 nodejs26.

NVD Description

Note: Versions mentioned in the description apply only to the upstream nodejs26 package and not the nodejs26 package as distributed by RHEL. See How to fix? for RHEL:10 relevant fixed versions and status.

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.

CVSS Base Scores

version 3.1