Node.js 26.13.1
The Node.js project released version 26.13.1 on November 11, 2026, a security-only patch for the LTS "Lithium" line that fixes sixteen CVEs, seven of them rated high severity. The release follows 26.13.0 by two weeks and touches the TLS, HTTP/2, HTTP, permission model, and zlib subsystems. No new APIs ship in this version.
What Changed
Almost every high-severity entry in the advisory list was fixed through private branches, which is typical for this cadence, and the credit lines point at Matteo Collina and Tim Perry for the TLS work. The larger share sits in HTTP/2 session handling:
- Header retention (CVE-2026-123863). Headers are now released when an HTTP/2 stream is removed, closing a leak that accumulated per stream.
- Abandoned streams (CVE-2026-123865). Node now detects HTTP/2 streams that nghttp2 abandoned and cleans up their resources.
- Pending write buffers (CVE-2026-123866, CVE-2026-123874). Buffers are retained until socket writes finish, and streams are retained during pending writes, preventing use of freed memory.
- Nested parser execution (CVE-2026-123864). Empty writes can no longer trigger nested parser execution in the TLS and HTTP layer.
- Memory accounting (CVE-2026-123868). Inbound DATA retained by streams is now charged to
maxSessionMemory, so a client cannot quietly exceed the configured ceiling. - ALTSVC overflow (CVE-2026-123828, medium). The ALTSVC buffer can no longer overflow.
The TLS fixes are grouped around session identity. TLS resumption is disabled for mutual TLS when no session id context is set, renegotiation and HelloRetryRequest can no longer change SNI, resumption can no longer change SNI, and the CA of an SNI context is applied even when that context has no certificate (CVE-2026-123872, CVE-2026-123867). A separate high-severity issue, CVE-2026-126051, fixes a remotely reachable crash in the TLS server.
Why It Matters
These are reachable from the network in the default configuration of any HTTPS or HTTP/2 server. The TLS resumption issues are the ones to read twice: if your service terminates TLS in Node and relies on session tickets with SNI-based certificate selection, the old behavior allowed a resumed session to present a different hostname than the one the session was established for. That is a certificate selection bypass in effect, and it is fixed here.
Two lower-severity entries affect the permission model. Denied descendants are no longer leaked in recursive fs.watch (CVE-2026-123829), and the heap snapshot destination is now permission-checked (CVE-2026-123873). A third low-severity fix handles a zlib params callback arriving after destroy (CVE-2026-123862). One medium HTTP fix redacts proxy credentials from invalid proxy URL error messages (CVE-2026-123871), which matters for anyone logging those errors verbatim.
Bundled Dependency Updates
Four dependency bumps ride along: brotli 1.2.1, llhttp 9.4.4, SQLite 3.54.1, and undici 8.12.4. The llhttp update is part of the HTTP parser surface fixed in this release. The SQLite bump brings the embedded node:sqlite module to 3.54.1, and undici 8.12.4 updates the bundled fetch implementation.
Upgrade Path
Node.js 26 entered long-term support as "Lithium" on October 28, 2026 and will receive updates through the end of April 2029. 26.13.1 is available now from nodejs.org and through the usual package managers. There are no breaking changes, no deprecations, and no configuration changes, so the upgrade is a version bump plus a restart. The project's guidance for security releases applies: treat this as urgent for anything listening on a network socket, especially services using HTTP/2 or TLS session resumption.
What's Next
Node.js 27 remains in the alpha channel, with 27.0.0-alpha builds published on October 29 and November 12. Nothing in this patch hints at a change to the 26.x schedule. Expect the next 26.x release in roughly two weeks unless another security report lands earlier.