Node.js vulnerabilities put HTTP/2 and HTTPS servers at risk
Node.js vulnerabilities in the runtime’s HTTP/2, HTTPS and TLS server code can let unauthenticated clients crash servers, exhaust their resources or read memory belonging to other connections. The Node.js project has released fixes for all three supported release lines: 22.23.5, 24.22.3 and 26.13.1.
HTTP/2 is the version of the web protocol used to exchange browser and server traffic, while a runtime is the software environment that runs an application. CVE-2026-123863 affects the built-in HTTP/2 support in the 24.x and 26.x lines. It can crash a default HTTP/2 server when the server sends a response before the complete request body has arrived, a behaviour the Node.js project describes as typical. An attacker does not need to log in, and the crash can be triggered over both encrypted TLS connections and cleartext connections.
A second HTTP/2 issue, CVE-2026-123866, can cause a server to send a client fragments of its memory, potentially including responses meant for other connections. It affects all three supported release lines. On versions from 24.22.0 and 26.9.0 onward, a client can trigger the problem by itself. On 22.x and older 24.x and 26.x builds, the server must also close a stream partway through a response, such as after an idle timeout. A stream is one exchange of data within an HTTP/2 connection.
CVE-2026-123864 affects Node.js HTTPS servers on all three supported lines. HTTPS is web traffic protected by TLS, the encryption system used to secure a connection. The flaw can allow an unauthenticated client to read memory from other connections, including TLS private keys and other users’ requests, according to the project. It requires an application handler to call res.flushHeaders() before the request body has fully arrived and later call res.end() with data. Reading the exposed memory also requires a route that sends back or stores a request body. Plain HTTP servers created with node:http are not affected.
The release addresses 16 vulnerabilities in Node.js, including seven rated high severity. Four other high-rated issues, alongside one medium-rated issue in the same area, affect particular server configurations. CVE-2026-123865 can make any default HTTP/2 server retain memory and file descriptors permanently on all three release lines. File descriptors are operating-system handles used for resources such as open connections and files.
CVE-2026-123874 can corrupt server memory on 24.x and 26.x when an application serves files with stream.respondWithFile() or stream.respondWithFD(). On all three lines, canceling those downloads can also crash the server under CVE-2026-123875, which is rated medium. CVE-2026-126051 can crash a TLS server on 24.x and 26.x when it uses the SNICallback, OCSPRequest, newSession or resumeSession hooks, or server.addContext(). These are server configuration and connection-handling features used by some Node.js applications.
The remaining high-rated issue, CVE-2026-123872, affects all three supported lines. On a TLS server that applies stricter client-certificate requirements to some hostnames, a client approved for one hostname can switch to a stricter hostname during TLS 1.2 renegotiation without satisfying that hostname’s requirements. A client certificate is a digital credential a server can require before allowing access, while renegotiation is a later adjustment of an existing TLS connection.
The eight issues described above are in Node.js’s own HTTP/2, HTTPS and TLS server code. They therefore matter when a Node.js process accepts those connections directly. The security advisory gives updating to the fixed version for the relevant release line as the only fix, and lists no workaround for servers that cannot update. End-of-life lines, including 20.x and 25.x, receive no fix in this release and the project says those versions are always affected.
The advisory does not report attacks exploiting these flaws. It also does not say whether operators whose servers met the conditions for the HTTPS memory exposure should replace TLS keys or other secrets after updating. Five of the vulnerabilities, including CVE-2026-123863 and CVE-2026-123864, were reported by Chris Rohlf in collaboration with Claude and Anthropic Research, according to the advisory.
For organisations running Node.js applications, AEU-I offers security-first IT, infrastructure and consulting, which is relevant when reviewing systems that accept HTTP/2, HTTPS or TLS connections. Operators should still follow the Node.js advisory and apply the fixed release themselves.
Users should first identify whether their website or application runs Node.js directly, then update to 22.23.5, 24.22.3 or 26.13.1 as appropriate. If an update cannot be made immediately, ask the hosting or application team whether the process accepts HTTP/2, HTTPS or TLS connections itself and whether the affected handlers and hooks are in use. Do not treat an end-of-life 20.x or 25.x installation as safe, because the project says those lines remain affected. After updating, review applications that handle request bodies, file downloads, TLS hostnames or client certificates, and ask the administrator whether any secrets need review because the advisory leaves TLS-key replacement unresolved.