Skip to content

Node.js 26.13.1 patches 16 bugs, seven of them high severity

The scheduled November security release lands across the 26.x, 24.x and 22.x lines, led by HTTP/2 use-after-free bugs and a TLS 1.2 renegotiation flaw that can bypass client certificate checks.

Source: Node.js

Node.js shipped its scheduled November security release today, patching 16 vulnerabilities across three supported lines: v26.13.1, v24.22.3 and v22.23.5. Seven of the fixes are rated High.

Most of the High-severity bugs sit in the HTTP/2 implementation: an assertion failure that lets a remote peer abort the process, a memory leak on protocol errors, and use-after-free issues in stream teardown and in respondWithFile(). The one worth checking first if you terminate TLS in Node: CVE-2026-123872 lets a client present a different certificate during TLS 1.2 renegotiation than the one checked at the initial handshake, which can undermine setups that rely on mutual TLS to pin a client’s identity.

nvm install 26.13.1  # or 24.22.3, 22.23.5

Why it matters: the HTTP/2 bugs give a remote peer a way to crash or leak memory in any server handling untrusted HTTP/2 traffic, and the renegotiation flaw is a real problem for anything that uses client certificates for auth over TLS 1.2. Upgrade to the patched point release for whichever major you run.

Share

Related reading

More from The Wire

All briefs