Node.js November 2026 Security Releases
16 CVEs. Seven High. All in the parts of Node.js that accept external connections.
TL;DR: On November 11, Node.js released security fixes for its 22.x, 24.x, and 26.x active LTS release lines. The patch covers 16 vulnerabilities across http2, https, tls, http, zlib, permission, and several dependencies (llhttp, undici, sqlite, brotli). Seven are rated High severity. The headline flaws are in HTTP/2: a reachable assertion lets unauthenticated clients crash any default server, a re-entrancy bug in HTTPS reads other connections’ heap memory including TLS private keys, and an HTTP/2 memory leak that never releases. All three active lines are affected. The fix version numbers: 22.23.5, 24.22.3, 26.13.1.
The HTTP/2 Cluster
Five of the seven High-rated flaws live in Node.js’s built-in HTTP/2 implementation. The common thread is stream lifecycle management: when a stream is removed from its session, the header buffers it holds must be released, or the session must detect that nghttp2 has already torn it down internally.
CVE-2026-123863 — HTTP/2 Crash (DoS, High)
A reachable assertion in ~Http2Session() lets any unauthenticated client crash the server over both TLS and cleartext connections.
The mechanics: When an Http2Stream is removed from the session’s stream set but its nghttp2-allocated header buffers aren’t detached, the stream retains a reference to those buffers. Later, when ~Http2Session() runs and finds current_nghttp2_memory_ is nonzero, the CHECK_EQ assertion fires and the process dies.
The trigger needs only a default HTTP/2 server that sends its response before the request body has fully arrived — which is the typical pattern for most APIs.
This is a variant of CVE-2024-27983 that the earlier fix missed because that fix only detached streams still tracked in the session. This one catches streams removed from the set but still holding buffers.
Affected: Node.js 24.x (since 24.22.0), 26.x (since 26.9.0)
CVE-2026-123866 — HTTP/2 Memory Leak (High)
A use-after-free in HTTP/2 stream teardown leaks response memory, including contents from other connections’ response buffers, to the peer.
The mechanics: When a stream is torn down while a response is still being written to the socket, the stream’s response buffer outlives the stream. If the socket later writes to a different stream, that stream reads the stale buffer — the contents of a completely different connection.
On Node.js 24.22.0+ and 26.9.0+, a client alone can trigger it. On 22.x and older builds, the server itself closing a stream partway (e.g., idle timeout) also triggers it.
Affected: All three lines (22.x, 24.x, 26.x)
CVE-2026-123865 — HTTP/2 Permanent Memory Leak (High)
An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a protocol error occurs during connection shutdown (oversized frame header), nghttp2 tears down the session internally but Node.js never notices, leaving a dangling session: the socket stays in CLOSE_WAIT and all HTTP/2 state for that connection is held indefinitely.
The attacker can trigger it remotely by sending GOAWAY(NO_ERROR), making it reliable against default servers. It’s an incomplete-fix case of CVE-2026-48937 — that fix detected nghttp2 internal terminations by watching for GOAWAY sent while not shutting down, but missed terminations arriving during shutdown.
Affected: All three lines
CVE-2026-123874 — HTTP/2 Server Memory Corruption (High)
A client can corrupt server memory on 24.x and 26.x when the server serves files with stream.respondWithFile() or stream.respondWithFD(). Canceling such downloads can also crash the server (CVE-2026-123875, rated Medium).
Affected: Node.js 24.x, 26.x
The HTTPS Re-entrancy Flaw
CVE-2026-123864 — HTTPS Memory Leak (High)
A re-entrancy flaw in Node.js HTTPS lets an unauthenticated client read memory belonging to other connections, including TLS private keys and other users’ requests.
The mechanics: TLSWrap::DoWrite() calls ClearOut() directly when asked to write zero bytes. If that write is issued from JavaScript running inside the HTTP parser’s on_body callback, ClearOut() decrypts the next TLS record while the parser is still mid-body, re-entering llhttp_execute() and causing a use-after-free followed by an out-of-bounds heap read. The server then copies that freed or unrelated heap memory into the response for the current request body.
Trigger: A handler that calls res.flushHeaders() before the request body ends, later calls res.end() with a non-empty chunk, and a route that echoes or stores a request body.
Cleartext node:http is not affected — only HTTPS servers.
Affected: All three lines (22.x, 24.x, 26.x)
Impact: This is the most dangerous of the batch. TLS private keys from other connections leaked to a client. The advisory does not say whether servers meeting the conditions should rotate their TLS keys after updating.
The TLS Fixes
CVE-2026-123872 — TLS Resumption SNI Change (High)
On a TLS server with stricter client-certificate rules for some hostnames, a client approved for another hostname can switch to a stricter one during TLS 1.2 renegotiation or via TLS resumption without meeting the stricter rules. Also covers mTLS with no session ID context.
Affected: All three lines
CVE-2026-126051 — TLS Server Crash (High)
A client can crash a TLS server on 24.x and 26.x if the server uses the SNICallback, OCSPRequest, newSession, or resumeSession hooks, or server.addContext().
Affected: Node.js 24.x, 26.x
The Medium and Low Flaws
CVE-2026-123828 — HTTP/2 ALTSVC Buffer Overflow (Medium)
CVE-2026-123867 — TLS SNI CA Without Certificate (Medium)
CVE-2026-123868 — HTTP/2 DATA Accounting (Medium)
CVE-2026-123871 — HTTP Proxy Credential Leak (Medium)
CVE-2026-123875 — HTTP/2 Null Write Request (Medium)
CVE-2026-123877 — HTTPS Agent TLS Policy Isolation (Medium)
CVE-2026-123829 — Permission fs.watch Leak (Low)
CVE-2026-123862 — Zlib Callback After Destroy (Low)
CVE-2026-123873 — Permission Heap Snapshot (Low)
These are mostly cleanup and edge-case fixes. The proxy credential leak (123871) is a visibility issue — credentials show up in error messages for invalid proxy URLs. The fs.watch leak (123829) shows denied descendant file paths in recursive watches.
Dependency Updates
The release also ships dependency bumps:
- llhttp to 9.4.4 (affects 22.x)
- undici to 8.12.4 (affects 24.x, 26.x)
- sqlite to 3.54.1 (affects 22.x, 24.x)
- brotli to 1.2.1
What This Means
You need to update. Three out of three lines.
Every actively supported Node.js line is affected. The HTTP/2 crash (123863) triggers on a default server that responds before the body finishes — that’s most API servers. The HTTPS memory leak (123864) affects every HTTPS server using the patterns described above. The permanent memory leak (123865) is a low-exploitation DoS that compounds over time.
Versions to update to:
- Node.js 26.x → 26.13.1
- Node.js 24.x → 24.22.3
- Node.js 22.x → 22.23.5
The fix was by Matteo Collina. Again.
Seven of the High-rated vulnerabilities were fixed by Matteo Collina (mcollina), Node.js core team member. He’s been fixing HTTP/2 lifecycle bugs across multiple releases. The common pattern: nghttp2 manages its own internal session state, and Node.js has to keep its stream set in sync. Every release finds a new corner of that sync problem.
No in-the-wild exploitation reported.
The advisory doesn’t mention observed exploitation. This is typical for Node.js security releases — the project patches proactively based on code review and testing rather than waiting for public PoCs.
No workarounds.
The advisory lists no workarounds for any of the seven High-rated flaws. Servers that cannot update immediately are exposed to the full set. If you can’t update, monitoring for HTTP/2 CLOSE_WAIT buildup (CVE-2026-123865) is a reasonable proxy for active exploitation.
Further Reading
- Node.js Security Releases (November 11, 2026)
- Node.js v26.13.1 LTS Release
- Node.js v24.22.3 LTS Release
- CVE-2026-123863 — HTTP/2 session teardown assertion
- The Hacker News coverage