Coordinated Node.js Security Patch: Fixing HTTP/2 Vulnerabilities and mTLS IsolationArticle · digest for November 12
Graphic illustration of a protected network gateway with closed locks and data streams
Article4 sections≈ 7 min

Coordinated Node.js Security Patch: Fixing HTTP/2 Vulnerabilities and mTLS Isolation

On November 11, 2026, the Node.js team issued coordinated out-of-band security updates for all supported runtime release lines. When a patch with only a third-digit version bump scrolls past in your feed, it's tempting to put off rebuilding containers until the next sprint. Yet when I opened the commit list compiled by release manager Antoine du Hamel, one detail stood out immediately: the vulnerabilities hit core network stream handling and certificate verification right at the front door of a server application.

The release patches a series of High- and Medium-severity flaws in the http2, tls, and http modules. Some bugs let an external client exhaust server memory using reset streams and empty writes until the OS kernel kills the process, while others allowed bypassing mutual TLS (mTLS) certificate verification by spoofing the hostname on the fly. Let's look at why these failures emerged at the boundary between JavaScript and C libraries, what they threaten in gateways, and how to update services smoothly.

Map of the November Patch: What Changed in Branches 22, 24, and 26

A coordinated patch release means the bugs sit in the platform's shared networking core. The November bundle targets three release lines:

  • Node.js 22.23.5 (LTS 'Jod') — the Maintenance LTS branch powering most conservative production services.
  • Node.js 24.22.3 (LTS 'Krypton') — the Active LTS branch for the main pool of modern projects.
  • Node.js 26.13.1 (LTS 'Lithium') — the newest active runtime line.

In the advisory, the team reiterates a strict rule: End-of-Life versions (including older 18.x and 20.x lines) always remain vulnerable when such releases ship, because no patches are produced for them. In our review of the major release wave of Node.js 22 LTS, 24 LTS, and 26 Current, we already looked at October's descriptor leak fixes and CONTINUATION frame protections, and the November bundle digs even deeper—into stream lifecycle mechanics between V8 and native code.

The HTTP/2 Multiplexing Trap: Abandoned nghttp2 Streams and Memory Leaks

Let's trace a typical API gateway to see where the cluster of vulnerabilities fixed by maintainer Matteo Collina came from. Suppose a Node.js service handling HTTP/2 traffic runs inside a container with a tight memory limit. Thanks to multiplexing over a single TCP connection, a client opens dozens of virtual streams in parallel, requesting data without extra handshakes.

Under the hood, frame parsing is handled by the C library nghttp2, while our code interacts with JavaScript objects. When a browser waits normally for a response, everything runs smoothly. But what happens if an external client opens hundreds of streams, sends headers or data, and immediately resets them before the response finishes?

Due to CVE-2026-123863 (High), http2 failed to release memory allocated for request headers during stream removal. At the same time, CVE-2026-123865 (High) kicked in: nghttp2 at the C layer already marked reset streams as abandoned streams, but the Node.js wrapper missed it and kept session structures alive. Making matters worse, CVE-2026-123868 (Medium) meant inbound DATA held by streams wasn't counted toward maxSessionMemory, so the server never saw the quota being exceeded.

Dead streams in the C native heap are invisible to V8's garbage collector.

For an attacker, this is a direct denial-of-service (DoS) vector: a burst of aborted requests inflates the process's native memory until the system OOM killer steps in.

A second group of bugs in the same subsystem stemmed from the reverse scenario—when a stream is destroyed before the socket finishes flushing the last bytes:

  1. Reset during active writes (CVE-2026-123866 and CVE-2026-123874, both High) — if a connection dropped during pending writes, the runtime could free a buffer or stream before the socket finished reading from memory. The patch keeps them alive until the write completes.
  2. Cancelled stream and buffer bugs (CVE-2026-123875 and CVE-2026-123828, both Medium) — added guards against dereferencing a null write request on a cancelled stream and against ALTSVC buffer overflows.
  3. Nested parsing on empty writes (CVE-2026-123864, High) — at the tls and http boundary, empty writes triggered recursive parser invocation inside the active processing loop.

In my view, the detail about retaining buffers when a stream closes illustrates a fundamental principle of systems engineering: in an asynchronous runtime, memory belongs not to the code that created the object, but to the slowest unfinished I/O operation. As long as the socket driver is reading bytes, the structure cannot be freed.

The mTLS Isolation Breach: How SNI Spoofing on Session Resumption Bypassed Certificate Checks

A second set of vulnerabilities, closed by Tim Perry and Matteo Collina, hit TLS encryption and mutual certificate authentication (mTLS). A single server process often serves several virtual hosts on the same port—for instance, a public perimeter and a private internal API requiring mTLS client certificates. So the server knows which domain a client is knocking on at the start of the handshake, TLS uses the SNI (Server Name Indication) extension—the hostname sent in the first packet.

Because certificate verification is CPU-intensive, TLS supports session resumption. It works like a paper wristband at a club entrance: show your ID once, get a wristband with a session ID, and walk back in without another check.

Right here, I noticed the sneakiest flaw in the release—CVE-2026-123872 (High). Session tickets in Node.js were not strictly bound to the virtual host:

  • Without a sessionIdContext parameter, a client could resume an open mTLS session in another context without re-verifying its certificate.
  • The runtime allowed changing the SNI domain name mid-flight—during TLS renegotiation, via a HelloRetryRequest (HRR), or during session resumption.

An attacker could complete a handshake on one host, obtain a session ticket, and then present it with an SNI header for a neighboring protected domain—bypassing certificate verification altogether.

Security caching without strict context binding turns an optimization into a backdoor.

In the new releases, mTLS session resumption is automatically disabled if sessionIdContext is not set, and changing SNI during renegotiation, HRR, or session resumption is blocked. Branches 24.22.3 and 26.13.1 also fix CVE-2026-126051 (High), which allowed crashing a TLS server remotely. Two more Medium-severity patches enforce Certificate Authority (CA) checks for SNI contexts without a certificate (CVE-2026-123867) and isolate TLS policy keys in the https.Agent pool (CVE-2026-123877). We covered earlier crypto module developments in our breakdown of the coordinated releases of Node.js 24.22.0 LTS and 26.12.0 Current.

Safe Upgrade Plan: Container Audit, TLS Settings, and Bundled Patches

The November release also closed related bugs. In http, CVE-2026-123871 (Medium) masks proxy credentials when parsing invalid proxy URLs so they no longer leak into logs. Rafael Gonzaga (RafaelGSS) fixed two Low-severity flaws in the Permission Model—leaking restricted subdirectories during recursive fs.watch (CVE-2026-123829) and skipping permission checks when writing a heap snapshot (CVE-2026-123873)—while zlib fixed invoking an options callback after stream destruction (CVE-2026-123862, Low). Across all three lines, llhttp was updated to 9.4.4 and built-in SQLite to 3.54.1 (branches 24 and 26 also bump Brotli to 1.2.1 and Undici to 7.30.2 and 8.12.4).

Node.js Safe Update Checklist

  • Update base images (node:22-alpine, node:24-alpine, node:26-bookworm) in Dockerfile and CI/CD to at least 22.23.5, 24.22.3, or 26.13.1.
  • Check tls.createServer configs in mTLS services: explicitly set a unique sessionIdContext string to keep session caching enabled.
  • Plan migrations off legacy 18.x and 20.x (EOL) branches onto supported LTS 22 or 24.

If your mTLS server previously lacked sessionIdContext, after patching the service will keep working, but it will disable the session cache and perform a full handshake on every request. Adding an explicit sessionIdContext string to your TLS options restores the original speed while preserving host isolation.

After upgrading to 22.23.5, 24.22.3, or 26.13.1, our example gateway is protected on both fronts: reset nghttp2 streams return memory to the OS immediately, incoming data stays within maxSessionMemory, and virtual hosts behind mTLS are isolated from SNI spoofing. Before closing your terminal, ask yourself one quick check: do you know the exact node -v inside your production containers, and is sessionIdContext set wherever services verify client certificates?

Want a deep diveVotes help us choose what to break down in detail. This material has 0 votes.
Sources · 4