CVE-2026-123862
Node.js is vulnerable to a zlib denial of service via a stream destroy during a pending params() call
An uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. zlib.params() queues a flush and completes its work in that write's callback; if the stream is destroyed first, as pipeline() does when the peer goes away, Writable still invokes the callback with an error, but the callback ignores its arguments and asserts that the native handle still exists. The handle is gone, so an ERR_INTERNAL_ASSERTION is thrown from inside stream internals and bypasses the stream's error event, the params() callback, and the pipeline() callback, terminating the process. An application is affected only if it calls deflate.params() while streaming to a peer, which is uncommon. This vulnerability affects Node.js 26.x, 24.x, and 22.x.
Fixes and workarounds
No remediation reported in collected sources.
Missing remediation information is not evidence that no patch exists.
Affected products and versions
| Product | Versions | Authority |
|---|---|---|
| node nodejs |
≥ 0.0.0; < 22.23.5 (affected, semver) ≥ 23.0.0; < 24.22.3 (affected, semver) ≥ 25.0.0; < 26.13.1 (affected, semver) Other versions: unaffected |
CNA: openjs |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 3.0 / 2.9 low |
CVSS:3.0/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L | CNA: openjs |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://nodejs.org/en/blog/vulnerability/november-2026-security-releasesCNA: openjs · vendor-advisory
- https://cna.openjsf.org/security-advisories.htmlCNA: openjs
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.