Skip to content
AIBRAINWORX / OpenSourceCoder.comLOCAL-FIRST. BUILT IN THE OPEN.
A.I. Cyber Security / Infrastructure & Data

Node.js Ships November 2026 Security Releases Patching Eight HTTP/2, HTTPS, and TLS Flaws

The Node.js Project issued November 11, 2026 security updates for its 26.x, 24.x, and 22.x release lines, patching eight HTTP/2, HTTPS, and TLS vulnerabilities alongside llhttp, undici, and sqlite updates.

Listen to this articleBrowser Voice
Ready
Official company logo or product image for nodejs-november-2026-security-releases-http2-https-tls-cves
Official image or organization logo from nodejs.org; identification only, no endorsement.
Event / context: 2026-11-11. Source check: October 28, 2026.

The Node.js Project has published its Wednesday, November 11, 2026 security releases, delivering patches across the active 26.x, 24.x, and 22.x runtime lines. The advisory addresses a cluster of remote crash, memory-leak, heap-disclosure, and authentication-bypass flaws inside the runtime's HTTP/2, HTTPS, and TLS subsystems, alongside dependency updates to resolve public vulnerabilities in llhttp, undici, and sqlite.

Core Release Scope and Security Attribution

In total, the disclosed Node.js advisory excerpt documents seven high-severity vulnerabilities and one medium-severity vulnerability affecting supported release branches. Across the eight entries, maintainers addressed three use-after-free defects, one reachable assertion abort, one permanent resource-leak state, one uncaught handshake exception, one TLS 1.2 client-certificate bypass, and one single-byte heap buffer overflow. Three of the high-severity HTTP/2 and HTTPS vulnerabilities—CVE-2026-123863, CVE-2026-123864, and CVE-2026-123874—were reported by security researcher Chris Rohlf in collaboration with Claude and Anthropic Research. Additional reports came from pimterry, aidan02, and zonduu, with fixes authored by Node.js maintainer mcollina and by pimterry. Dependency updates ship concurrently for llhttp on 22.x, 24.x, and 26.x, undici on 24.x and 26.x, and sqlite on 22.x and 24.x.

HTTP/2 Memory Accounting and Stream Teardown Architecture

Five of the disclosed flaws target Node.js's C++ HTTP/2 integration built atop nghttp2. Under CVE-2026-123863, affecting 24.x and 26.x over both TLS and cleartext, an unauthenticated client can force a server process abort when an Http2Stream retaining nghttp2-allocated header buffers outlives its parent session. Because the stream is removed from the session's stream set without being detached, ~Http2Session() encounters nonzero memory accounting and trips CHECK_EQ(current_nghttp2_memory_, 0). The advisory notes this is a variant of CVE-2024-27983 whose prior fix only detached streams still tracked by the session.

Two additional HTTP/2 flaws stem from stream teardown and shutdown transitions. Under CVE-2026-123865, affecting 22.x, 24.x, and 26.x, an attacker can send GOAWAY(NO_ERROR) to initiate shutdown and then inject a protocol error such as an oversized frame header. While nghttp2 terminates internally, Node.js misses the termination—an incomplete-fix case of CVE-2026-48937—leaving the socket permanently in CLOSE_WAIT and leaking session memory and file descriptors. Under CVE-2026-123866, also spanning 22.x, 24.x, and 26.x, tearing down a stream during a backpressured write causes freed response buffers or unrelated heap memory to be transmitted to the peer. On 26.x and 24.x, remote peers can drive that teardown via RST_STREAM once the window-size change from 26.9.0 and 24.22.0 is present, while all supported lines remain reachable through application-initiated teardowns such as per-stream idle timeouts.

Rounding out the HTTP/2 disclosures, CVE-2026-123874 on 24.x and 26.x introduces a use-after-free when a client resets a stream while a write from stream.respondWithFile() or stream.respondWithFD() remains queued, leading to a dereference and virtual call on a freed Http2Stream. Meanwhile, the medium-severity CVE-2026-123828 on 24.x and 26.x exposes a one-byte heap-buffer-overflow in src/node_http2.cc inside Http2Session.altsvc(), where a buffer sized to an origin string's length is written with a null terminator, corrupting heap memory and aborting the process.

HTTPS Re-Entrancy and TLS Handshake Vulnerabilities

Beyond HTTP/2, the advisory details three high-severity flaws in TLS and HTTPS handling. In CVE-2026-123864, affecting 22.x, 24.x, and 26.x, TLSWrap::DoWrite() invokes ClearOut() directly when instructed to write zero bytes. If JavaScript executes that write inside the HTTP parser's on_body callback, ClearOut() decrypts the subsequent TLS record mid-body and re-enters llhttp_execute(), triggering a use-after-free and an out-of-bounds heap read. Because the server then copies freed or unrelated heap memory—potentially containing TLS private keys or other users' requests—into the request body, ordinary echo or storage routes leak cross-connection data. Cleartext node:http is not affected.

In the TLS layer itself, CVE-2026-126051 on 24.x and 26.x targets servers configuring SNICallback, OCSPRequest, newSession, resumeSession, or server.addContext(). A crafted client hello—such as omitting SNI alongside an OCSP request, padding, and a socket FIN—causes OpenSSL to deliver handshake data and end-of-file in the same tick, destroying the socket before deferred callbacks run and raising an uncaught exception rather than emitting an error event. Finally, CVE-2026-123872 across 22.x, 24.x, and 26.x allows clients on TLS 1.2 connections to switch servernames unilaterally during renegotiation, carrying prior authentication across hostnames to bypass stricter per-host client-certificate policies.

Operational Impact on Production Deployments

Several of these vulnerabilities require minimal preconditions, making timely runtime upgrades critical for internet-facing services. Default HTTP/2 servers become vulnerable to remote aborts under CVE-2026-123863 whenever a handler responds before the incoming request body finishes, and default file-serving handlers using respondWithFile() or respondWithFD() expose memory corruption under CVE-2026-123874. Applications passing untrusted values such as a request's :authority header into session.altsvc() face single-request crashes or heap corruption under CVE-2026-123828.

For HTTPS APIs, handlers that call res.flushHeaders() before the request body completes and later invoke res.end() with a non-empty chunk must prioritize patching CVE-2026-123864 to stop cross-connection heap leakage. Operators terminating TLS directly in Node.js should also review whether multi-host virtual servers enforce differing client-certificate requirements over TLS 1.2 under CVE-2026-123872, or rely on asynchronous SNI and OCSP hooks exposed to unauthenticated handshakes under CVE-2026-126051. Engineering teams upgrading runtimes should likewise verify application compatibility with the bundled llhttp, undici, and sqlite dependency updates.

Release Boundaries, Lifecycle Caveats, and Source Limits

Exposure varies meaningfully across active branches. While Node.js 24.x and 26.x are affected by all eight documented vulnerabilities, the 22.x line is unaffected by CVE-2026-123863, CVE-2026-126051, CVE-2026-123874, and CVE-2026-123828, while still requiring patches for the remaining four flaws alongside llhttp and sqlite updates. Deployments running Node.js versions past the Maintenance LTS phase receive no upstream fixes in this release cycle; The Node.js Project notes that commercial support for end-of-life releases is available through OpenJS Ecosystem Sustainability Program partners.

This report is grounded strictly in The Node.js Project's published advisory text and does not reflect independent exploit reproduction or runtime benchmarking. Because the provided primary text excerpt terminates immediately after CVE-2026-123828, operators should consult the full upstream announcement for exact point-release version numbers, verification checksums, and any trailing advisory notices.

Automated Vertex AI (gemini-4-hydrogen) primary-source report; reviewed 2026-11-19.

Follow your curiosity.

Pass the signal.