Security · · 6 min read

Node.js November 2026 Security Release: an HTTPS Heap Leak, an mTLS Bypass and a Pile of HTTP/2 Crashes

Node.js 22.23.5, 24.22.3 and 26.13.1 fix 17 CVEs, seven of them rated high. The worst lets a client read other connections' memory, including TLS private keys, from an HTTPS server. Several were found by Anthropic Research working with Claude.

Gouache-style illustration of eight slate-blue pipes hanging in a row from a dark rail against a pale wall, one pipe painted terracotta with three small ochre drops falling from its end onto a sage floor
Illustration by TechPulse Editorial · Eight streams on one rail, and one that leaks what it shouldn't.
Severity
HIGH · CVSS 8.1
Affected
Node.js 22.x < 22.23.5, 24.x < 24.22.3, 26.x < 26.13.1; end-of-life lines are also affected
Patched
22.23.5, 24.22.3, 26.13.1

Three weeks after the October Brotli emergency, the Node.js project is back with another security release. On November 11, 2026 it shipped v22.23.5, v24.22.3 and v26.13.1. The releases fix 17 CVEs: seven high, six medium and four low. Nothing is rated critical, but the high ones are remotely reachable, and several need nothing more than a default server.

The release also updates bundled dependencies: llhttp 9.4.4 on all lines, undici 8.12.4 on 24.x and 26.x (which carries six of its own cache and redirect fixes) and sqlite 3.54.1 on 22.x and 24.x.

A detail worth noticing: five of the CVEs, including the worst one, credit Chris Rohlf in collaboration with Claude and Anthropic Research.

The one to read first: HTTPS heap leak (CVE-2026-123864)

This is a re-entrancy bug in the HTTPS stack. When JavaScript running inside the HTTP parser’s on_body callback triggers a zero-length TLS write, TLSWrap::DoWrite() calls ClearOut() directly. That decrypts the next TLS record while the parser is still in the middle of the body, re-entering llhttp_execute(). The result is a use-after-free and an out-of-bounds heap read, and the server copies that memory into the request body.

The advisory says an unauthenticated client can read memory belonging to other connections, including TLS private keys and other users’ requests. The conditions:

  • a handler that calls res.flushHeaders() before the request body ends and later calls res.end() with a non-empty chunk, and
  • any ordinary route that echoes or stores a request body, so the attacker can read the leaked bytes back.

It affects 22.x, 24.x and 26.x. Plain-text node:http is not affected. NVD-sourced trackers list it at CVSS 8.1.

Authentication bypasses in TLS

  • CVE-2026-123872 (high, 8.1): on a server with different client-certificate policies per hostname, a client that authenticated for an allowed host can renegotiate TLS 1.2 under a different servername and carry its authentication to the stricter host. The fix blocks SNI changes through renegotiation, HelloRetryRequest and session resumption, and disables resumption for mTLS without a session id context. All lines.
  • CVE-2026-123867 (medium): if you call server.addContext(host, { ca: protectedCA }) without a server certificate in that context, the per-host CA is never installed and the handshake falls back to the default client CA. A client trusted only by the default CA can complete mTLS to the protected host.
  • CVE-2026-123877 (medium): https.Agent gave the same session-cache key to a request that omits ca and one that passes ca: []. With TLS 1.3 resumption, the stricter request could reuse a session authenticated under the default trust store.

HTTP/2: crashes, leaks and use-after-frees

CVESeverityWhat a remote client can doLines
CVE-2026-123863HighAbort the server via a failed memory-accounting assertion in ~Http2Session(); needs only a handler that responds before the body ends24, 26
CVE-2026-123865HighLeak memory and file descriptors forever by triggering a protocol error during shutdown (start it with GOAWAY(NO_ERROR))22, 24, 26
CVE-2026-123866HighReceive freed response memory from other connections when a backpressured stream is torn down22, 24, 26
CVE-2026-123874HighUse-after-free when a respondWithFile() stream is reset during a pending write24, 26
CVE-2026-123828MediumOne-byte heap overflow in session.altsvc() with a long :authority24, 26
CVE-2026-123868MediumExhaust memory; queued inbound DATA was never charged to maxSessionMemory24, 26
CVE-2026-123875MediumCrash file-serving handlers by cancelling a few downloads22, 24, 26

On the TLS side, CVE-2026-126051 (high) lets a client crash a server that uses SNICallback, OCSPRequest, newSession, resumeSession or server.addContext(): the socket is destroyed before a deferred handshake callback runs, and the process throws an uncaught exception.

The lower-severity fixes include proxy credentials leaking into ERR_PROXY_INVALID_CONFIG messages (CVE-2026-123871), a zlib params() + destroy() crash (CVE-2026-123862) and several Permission Model gaps, among them a wildcard --allow-fs-read rule that also matched the bare path (CVE-2026-106071).

What to do

  1. Upgrade to 22.23.5, 24.22.3 or 26.13.1, and rebuild container images that pin a Node patch version. End-of-life lines are affected and get no fix.
  2. If you terminate HTTPS or HTTP/2 directly in Node rather than behind a proxy, treat this as urgent. Exposure is much higher than for apps behind a load balancer that speaks HTTP/1.1 to the backend.
  3. If you rely on per-host mTLS (addContext with different CAs), check after upgrading that every protected context carries its own certificate and that TLS 1.2 renegotiation is not needed by your clients.
  4. If you can’t patch immediately, put a reverse proxy in front that terminates TLS and HTTP/2. That removes the remote paths for most of the high-severity bugs.

Sources & Primary Advisories

  1. Node.js — Wednesday, November 11, 2026 Security Releases
  2. Node.js — Node.js 26.13.1 (LTS) release notes
  3. Rapid7 — CVE-2026-123872
  4. vuln.today — Node.js CVE-2026-123864 (HIGH 8.1)
  5. undici v8.12.4 release (bundled in 24.x and 26.x)
Share Dispatch