Node.js November 2026 Security Releases (v26.13.1, v24.22.3, v22.23.5) Deep Dive: HTTPS Heap Leaks, HTTP/2 Teardown Crashes, and mTLS Bypasses
An in-depth engineering breakdown of the 16 CVEs patched in Node.js v26.13.1, v24.22.3, and v22.23.5 (November 2026 Security Releases), covering HTTPS llhttp_execute() re-entrancy heap leaks (CVE-2026-123864), HTTP/2 session teardown aborts and UAFs (CVE-2026-123863, CVE-2026-123866), TLS 1.2 renegotiation mTLS bypasses (CVE-2026-123872), and a static CI audit script.
Conceptual architecture diagram of the 16 CVEs patched in Node.js 26.13.1, 24.22.3, and 22.23.5 across HTTPS/TLS, HTTP/2, and Permission subsystems
The Node.js project published its November 11, 2026 Security Releases—shipping v26.13.1 'Lithium' (LTS), v24.22.3 'Krypton' (LTS), and v22.23.5 'Jod' (LTS)—to patch 16 vulnerabilities (7 High, 6 Medium, and 3 Low severity) alongside bundled dependency updates (llhttp 9.4.4, undici 8.12.4, sqlite 3.54.1, and brotli 1.2.1). National CERT advisories, including KrCERT/CC's security notice, followed immediately because several of the flaws—discovered in collaboration with Anthropic Research and Trail of Bits (OpenAI)—allow unauthenticated remote attackers to crash HTTP/2 and TLS servers or read heap memory belonging to other connections.
The key operational takeaway is straightforward: all seven High-severity vulnerabilities reside in Node.js's built-in node:http2, node:https, and node:tls server stacks, and the official advisory provides no configuration workaround short of upgrading the runtime binary. Most critically, CVE-2026-123864 (HTTPS parser re-entrancy on zero-length TLS writes) and CVE-2026-123866 (HTTP/2 stream teardown use-after-free under write backpressure) can copy freed or cross-connection heap memory—including other users' requests and TLS private keys—into outbound responses. Operators running affected versions on direct TLS or HTTP/2 listeners must upgrade to v26.13.1, v24.22.3, or v22.23.5 immediately and evaluate TLS key and secret rotation if trigger conditions were reachable. This analysis cross-references the official Node.js Security Advisory and release notes as of November 18, 2026; we do not execute live exploit payloads against production targets and instead provide a safe static audit script for CI/CD pipelines.
1. Beyond Process Crashes: Cross-Connection Heap Memory Disclosure
While denial-of-service assertions require urgent patching, two High-severity defects in this release cross the boundary into remote memory disclosure across concurrent connections:
- HTTPS Zero-Length TLS Write Re-Entrancy into
llhttp_execute()(CVE-2026-123864, High — 22.x / 24.x / 26.x): - Mechanism: Inside Node.js's TLS binding,
TLSWrap::DoWrite()invokesClearOut()synchronously whenever it is asked to write zero bytes. If application JavaScript running inside the HTTP parser'son_bodycallback triggers a zero-byte write,ClearOut()decrypts the next incoming TLS record whilellhttpis still mid-body, re-enteringllhttp_execute(). - Impact: Re-entering the parser triggers a use-after-free (UAF) and an out-of-bounds (OOB) heap read, causing the server to copy unrelated heap memory—including TLS private keys and other users' in-flight requests—into the request body buffer.
- Preconditions: Triggering the bug requires an HTTPS route that calls
res.flushHeaders()before the request body finishes and later callsres.end()with a non-empty chunk, paired with any ordinary route that echoes or stores a request body. Cleartextnode:httpis not affected. Node.js November 2026 Security Advisory
- HTTP/2 Stream Teardown Use-After-Free Under Backpressure (
CVE-2026-123866, High — 22.x / 24.x / 26.x): - Mechanism: When an
Http2Streamis torn down while a socket write is backpressured—either via a peer-sentRST_STREAMor a server-side per-stream idle timeout—the stream's response buffer is freed, but a dangling reference is still written to the socket. - Impact: Freed heap memory or response buffers belonging to other connections are transmitted to the client. On Node.js
26.x(since26.9.0) and24.x(since24.22.0), a remote peer can drive this teardown directly; on all three active LTS lines, application-initiated stream timeouts can hit the same path.
2. Four Technical Boundaries That Determine Your Exposure
Before rolling out emergency restarts across every cluster, separate your services along four architectural boundaries:
- Reverse-proxied cleartext
node:httpbackends vs. direct TLS / HTTP/2 termination: All High-severity bugs target Node.js's own C++/JS protocol handlers for HTTP/2, HTTPS, and TLS. If an edge proxy (such as Envoy, Nginx, AWS ALB, or Cloudflare) terminates TLS and HTTP/2 and forwards traffic to Node.js strictly over cleartext HTTP/1.1 (node:http) inside a trusted network, external clients cannot directly trigger these protocol state machines. Conversely, Node.js processes that terminate public HTTPS, gRPC over HTTP/2, or mTLS connections directly are exposed on the front line.
- 24.x / 26.x-specific regressions vs. all-LTS vulnerabilities: Five CVEs—
CVE-2026-123863,CVE-2026-126051,CVE-2026-123874,CVE-2026-123828, andCVE-2026-123868—affect 24.x and 26.x only, whereas the remaining 11 CVEs (includingCVE-2026-123864,CVE-2026-123865,CVE-2026-123866, andCVE-2026-123872) impact 22.x, 24.x, and 26.x alike. NVD CVE-2026-123863
maxSessionMemoryconfiguration vs. undrained HTTP/2 stream queues (CVE-2026-123868): SettingmaxSessionMemoryon an HTTP/2 server did not protect unpatched 24.x and 26.x processes against inbound queue exhaustion. Each 1-byte DATA frame queued on an undrained stream cost the attacker roughly 10 wire bytes while retaining roughly 114 bytes of JSBufferview metadata on the server without chargingcurrent_session_memory_.
- Installed host package version vs. live container / worker runtime binary: Updating a base package or VM image does not patch long-running PM2 workers or pinned container digests, and End-of-Life (EOL) lines such as Node.js 20.x and 25.x receive no patches at all. Always verify the live process via
process.versions.node.
| CVE ID | Severity | Affected Lines | Subsystem | |
| CVE-2026-123863 | High | 24.x, 26.x | http2 | When a handler responds before the request body ends, a removed Http2Stream can outlive its session while holding nghttp2 header buffers, failing CHECK_EQ(current_nghttp2_memory_, 0) in ~Http2Session() and aborting the process (variant of CVE-2024-27983) |
| CVE-2026-123864 | High | 22.x, 24.x, 26.x | https / tls | A zero-length TLS write inside on_body (e.g., res.flushHeaders() before body end + res.end(chunk)) calls ClearOut() and re-enters llhttp_execute(), causing UAF/OOB reads that copy other requests or TLS private keys into the response |
| CVE-2026-123865 | High | 22.x, 24.x, 26.x | http2 | Triggering a protocol error (such as an oversized frame header) after initiating shutdown with GOAWAY(NO_ERROR) leaves sockets stuck in CLOSE_WAIT and leaks session memory/FDs permanently (incomplete fix of CVE-2026-48937) |
| CVE-2026-123866 | High | 22.x, 24.x, 26.x | http2 | Tearing down a stream during write backpressure (via peer RST_STREAM or stream timeout) frees the response buffer while a queued write still references it, leaking heap memory to the peer |
| CVE-2026-126051 | High | 24.x, 26.x | tls | Deferred handshake hooks ( SNICallback, OCSPRequest, newSession, resumeSession, server.addContext()) throw an uncaught exception if the client sends a socket FIN in the same tick as ClientHello |
| CVE-2026-123872 | High | 22.x, 24.x, 26.x | tls | Clients can switch servername (SNI) during TLS 1.2 renegotiation, HRR, or session resumption to carry client-cert authentication from a permissive host to a stricter mTLS host |
| CVE-2026-123874 | High | 24.x, 26.x | http2 | Resetting a stream.respondWithFile() or respondWithFD() stream while a write is queued frees Http2Stream before completion, triggering a virtual call through freed memory (UAF) |
| CVE-2026-123828 | Medium | 24.x, 26.x | http2 | Passing a long attacker-controlled origin (such as :authority) to session.altsvc() writes a null terminator one byte past the allocated heap buffer |
| CVE-2026-123867 | Medium | 22.x, 24.x, 26.x | tls | Calling server.addContext(host, { ca }) without a server certificate causes setSniContext to return false and silently fall back to the default client CA, bypassing per-host mTLS |
| CVE-2026-123868 | Medium | 24.x, 26.x | http2 | Inbound DATA frames queued on an undrained stream (~114B retained per 10B 1-byte frame) bypass current_session_memory_ and maxSessionMemory admission checks |
| CVE-2026-123871 | Medium | 22.x, 24.x, 26.x | http | Four unredacted error paths interpolate raw proxy URLs (including usernames and passwords) into ERR_PROXY_INVALID_CONFIG error messages and logs (missed paths from CVE-2026-48615) |
| CVE-2026-123875 | Medium | 22.x, 24.x, 26.x | http2 | Cancelling an active respondWithFile() or respondWithFD() transfer tears down StreamPipe out of order, causing a NULL pointer dereference crash |
| CVE-2026-123877 | Medium | 22.x, 24.x, 26.x | https | https.Agent.prototype.getName() generates identical session-cache keys when ca is omitted vs. ca: [], allowing TLS 1.3 session resumption to bypass stricter custom CA policies |
| CVE-2026-123829 | Low | 22.x, 24.x, 26.x | permission / fs | Recursive fs.watch() on macOS/Windows under --permission checks read grants only on the root directory and leaks relative filenames created inside denied subdirectories |
| CVE-2026-123862 | Low | 22.x, 24.x, 26.x | zlib | Peer disconnect during a pending deflate.params() flush destroys the stream first and triggers an uncatchable ERR_INTERNAL_ASSERTION |
| CVE-2026-106071 / 123873 | Low | 22.x, 24.x, 26.x | permission | Radix-tree wildcard lookup over-grants shorter prefix paths (e.g., --allow-fs-read=/etc/passwd.* matching /etc/passwd) plus missing permission checks on heap snapshot destinations |
Note that while the main November 2026 Security Advisory details CVE-2026-106071, the individual release changelogs (v26.13.1, v24.22.3, v22.23.5) also list CVE-2026-123873 (permission: check heap snapshot destination) alongside dependency upgrades to llhttp 9.4.4, sqlite 3.54.1, and (on 24.x and 26.x) undici 8.12.4 and brotli 1.2.1.
3. Deep Dive: HTTP/2 Session Accounting & mTLS Policy Bypasses
3.1 HTTP/2 Session & Stream Lifecycle Mismatches (CVE-2026-123863 · 123865 · 123874 · 123875)
Node.js's node:http2 implementation bridges JavaScript streams, C++ Http2Session/Http2Stream objects, and the underlying nghttp2 C state machine. Four of the November patches fix lifecycle desynchronizations when streams or sessions close early:
- Orphaned Header Buffers Outliving
Http2Session(CVE-2026-123863): - The earlier fix for
CVE-2024-27983detached streams during session teardown, but only iterated over streams still present in the session's active stream set. - When an HTTP/2 server responds before the request body has finished—a standard pattern for early auth rejections, redirects, or payload-size checks—a client can cause an
Http2Streamto be removed from the session's stream set while still holdingnghttp2-allocated header buffers. When~Http2Session()runs,current_nghttp2_memory_is non-zero andCHECK_EQ(current_nghttp2_memory_, 0)aborts the entire Node.js process.
- Silent
nghttp2Termination During Shutdown (CVE-2026-123865): - The prior patch for
CVE-2026-48937watched for internalnghttp2session terminations only when the session was not already shutting down. - By sending
GOAWAY(NO_ERROR)first to enter the shutdown state and then sending a malformed frame (such as an oversized frame header), an unauthenticated client causesnghttp2to terminate internally without notifying Node.js. The TCP socket stays wedged inCLOSE_WAITand leaks memory and file descriptors indefinitely.
- File Streaming Teardown Races (
CVE-2026-123874&CVE-2026-123875): - Serving files via
stream.respondWithFile()orstream.respondWithFD()exposes two teardown hazards when a client cancels or resets the stream mid-transfer: on 24.x and 26.x, a pending socket write completion invokes a virtual method on a freedHttp2Stream(CVE-2026-123874), while on all active linesStreamPipeteardown ordering leaves a NULL pointer that crashes the server (CVE-2026-123875).
3.2 Three TLS / mTLS Policy Isolation Bypasses (CVE-2026-123872 · 123867 · 123877)
Multi-tenant TLS servers and zero-trust mTLS clients face three distinct authentication bypasses in unpatched builds:
- Unilateral SNI Switching Across TLS 1.2 Renegotiation & Resumption (
CVE-2026-123872): On a server enforcing stricter client-certificate rules on specific hostnames (e.g., an admin SNI host vs. a general API host), a client could authenticate against the permissive host and then changeservernameduring TLS 1.2 renegotiation, HelloRetryRequest (HRR), or session resumption—carrying its existing authentication into the restricted host. The fix disables session resumption for mTLS when no session ID context is set and blocks SNI changes across renegotiation, HRR, and resumption. Node.js v26.13.1 Release Notes
- CA-Only SNI Contexts Failing Open to the Default CA (
CVE-2026-123867): When a server registers per-host client CAs viaserver.addContext(host, { ca: protectedCA })without supplying a separate server certificate in that SNI context,setSniContextinsrc/crypto/crypto_tls.ccreturnedfalseandCertCbDoneskipped installing the custom client CA—allowing clients signed by the default CA to passrequestCertandrejectUnauthorized.
- Outbound
https.AgentSession Cache Key Collision (CVE-2026-123877): Becausehttps.Agent.prototype.getName()serialized both an omittedcaoption and an explicitca: []array to the same empty string in the agent key, a TLS 1.3 session established under the system trust store could be reused by a subsequent request configured withca: [].
4. Automated Runtime & Source Pattern Audit Scripts
4.1 One-Liner Runtime & Dependency Verification
Verify the live binary and bundled native dependencies inside every running container, VM, or worker process:
Confirm that your runtime meets or exceeds these patched baselines:
- Node.js 26.x:
26.13.1or newer (llhttp 9.4.4,undici 8.12.4,sqlite 3.54.1,brotli 1.2.1) — v26.13.1 Release Notes
- Node.js 24.x:
24.22.3or newer (llhttp 9.4.4,undici 8.12.4,sqlite 3.54.1,brotli 1.2.1) — v24.22.3 Release Notes
- Node.js 22.x:
22.23.5or newer (llhttp 9.4.4,sqlite 3.54.1) — v22.23.5 Release Notes
4.2 CI/CD Static Scanner for Vulnerable API Patterns (Python)
Use the standalone Python script below (audit_nodejs_nov2026_cves.py) in CI to flag unpatched runtime versions and identify code paths that exercise flushHeaders(), respondWithFile(), altsvc(), server.addContext(), or deferred TLS hooks:
5. Production Remediation Checklist
Verify live runtime versions and retire EOL lines: Check process.versions.node across all running pods, VMs, and background workers to confirm v26.13.1+, v24.22.3+, or v22.23.5+, and migrate any remaining 20.x or 25.x workloads to an active LTS line. Node.js Security Advisory
Prioritize internet-facing HTTP/2 and HTTPS listeners: Patch Node.js services that accept external HTTP/2, gRPC, HTTPS, or TLS connections directly before internal-only workers. If an immediate binary upgrade is blocked, terminate TLS and HTTP/2 at an upstream reverse proxy and forward only cleartext HTTP/1.1 over an isolated network until patched.
Evaluate TLS private key and secret rotation (CVE-2026-123864 & CVE-2026-123866): If an unpatched HTTPS server combined early res.flushHeaders() with request-body echoing/storage, or an HTTP/2 service experienced frequent stream resets/timeouts under write backpressure, rotate TLS certificates, private keys, and session signing secrets after upgrading.
Audit per-host mTLS and server.addContext() rules (CVE-2026-123872 & CVE-2026-123867): Ensure every server.addContext() call includes a server certificate (cert and key) alongside any custom ca override, and configure explicit sessionIdContext values for mTLS endpoints.
Scrub log aggregators for leaked proxy credentials (CVE-2026-123871): Search centralized logging and crash-reporting pipelines for ERR_PROXY_INVALID_CONFIG entries that may have captured raw proxy URLs containing credentials, and rotate any exposed proxy tokens or passwords.
6. Official References (Verified 2026-11-18)
Verified on: November 18, 2026
Korean version:
Node.js 11월 보안 패치(v26.13.1·v24.22.3·v22.23.5) 16개 CVE 심층 분석: HTTPS 힙 메모리 유출·HTTP/2 원격 크래시·mTLS 우회 점검하기