Node.js updates supported releases to address 16 server vulnerabilities

Node.js releases patches for HTTP/2, HTTPS and TLS flaws
The Node.js project has released versions 22.23.5, 24.22.3 and 26.13.1 to correct 16 vulnerabilities in the runtime. Seven are rated high severity. The issues affect Node.js processes that accept connections through the runtime’s own HTTP/2, HTTPS or TLS server code, with consequences ranging from service crashes and resource retention to disclosure of memory associated with other connections.
The most significant issues include two HTTP/2 flaws. CVE-2026-123863 permits an unauthenticated client to crash a server on the 24.x and 26.x lines when a default HTTP/2 server sends a response before it has received the entire request body. Node.js describes that response pattern as typical. The problem can be triggered over both TLS and cleartext HTTP/2 connections.
CVE-2026-123866, which affects all three supported lines, may make a server send a client portions of its memory, including responses intended for other connections. On 24.22.0 and 26.9.0 and later, a client can trigger the condition on its own. On 22.x and older affected 24.x and 26.x builds, the server can also create the condition by closing a stream partway through a response, such as after an idle timeout.
HTTPS memory exposure has narrow but serious prerequisites
A separate high-severity issue, CVE-2026-123864, affects HTTPS servers on all supported lines. An unauthenticated client may read memory belonging to other connections, potentially including TLS private keys and other users’ requests. The affected pattern requires a handler to call res.flushHeaders() before a request body has fully arrived and later call res.end() with data. Recovering leaked memory also requires a route that returns or stores a request body.
Plain HTTP servers created with node:http are not affected by that HTTPS flaw. The distinction matters for inventory work: exposure depends on a Node.js process directly accepting the affected HTTP/2, HTTPS or TLS traffic and, for some issues, on the server’s implementation choices.
Other high-rated bugs affect resources, file delivery and TLS handling
CVE-2026-123865 can let a client cause any default HTTP/2 server on all three supported lines to retain memory and file descriptors permanently. On 24.x and 26.x, CVE-2026-123874 can corrupt server memory when applications deliver files with stream.respondWithFile() or stream.respondWithFD(). Cancelling those downloads can also crash servers on all supported lines through CVE-2026-123875, rated medium.
Node.js also fixed CVE-2026-126051, which can crash TLS servers on 24.x and 26.x when they use hooks including SNICallback, OCSPRequest, newSession or resumeSession, or use server.addContext(). CVE-2026-123872 affects TLS servers that apply stricter client-certificate rules to selected hostnames: during TLS 1.2 renegotiation, a client accepted for one hostname can switch to a stricter hostname without satisfying its rules.
The security advisory lists updating as the only remediation and provides no workaround for systems that cannot yet move. End-of-life lines, including 20.x and 25.x, receive no fix and are described as always affected. The advisory reports no attacks using these flaws and does not state whether organisations meeting the HTTPS leak conditions should rotate TLS keys or other secrets after patching. For businesses, the immediate action is to map internet-facing Node.js services, upgrade each supported line to its fixed release, and assess affected HTTPS handlers for possible exposure before closing the incident work.

