Skip to content
Sandeep Kumar
Security

Node.js security releases: 16 fixes, mostly HTTP/2 and TLS

Node.js 22.23.5, 24.22.3 and 26.13.1 fix 16 vulnerabilities, seven rated high. Node 20 and older get nothing. What changed and how to upgrade.

Act now

Act now: Upgrade to 22.23.5, 24.22.3 or 26.13.1, first on servers that speak HTTP/2 or terminate TLS in Node. On Node 20 or older, move to a supported line.

Sandeep Kumar, Full-stack EngineerSandeep KumarFull-stack Engineer

Node.js released security updates for all three supported lines on 11 November 2026: v22.23.5, v24.22.3 and v26.13.1. They fix 16 vulnerabilities, seven of them rated high.

If your server speaks HTTP/2 or terminates TLS in Node itself, upgrade this week. If it sits behind Nginx or a load balancer that handles both, it's less urgent, but still do it.

Where the bugs are

Most of the high-severity bugs are in HTTP/2 stream and session handling:

  • one remote abort
  • two bugs that could leak server memory to the other end of the connection
  • a use-after-free when a respondWithFile() stream is reset mid-write
  • sessions that never clean up after a protocol error during shutdown

On the TLS side, one high-severity bug lets a client change the servername through TLS 1.2 renegotiation and get around client-certificate authentication. Another makes a TLS server throw an uncaught exception from deferred handshake callbacks, which crashes the process.

The medium and low fixes include:

  • proxy credentials appearing in ERR_PROXY_INVALID_CONFIG error messages
  • certificate validation skipped when https.Agent reuses a TLS session across policies
  • two Permission Model bypasses

Bundled llhttp, undici and SQLite were updated too.

Not every line was hit equally. Node 24 and 26 carry all 16; Node 22 carries 11.

Upgrade

bash
node -v                 # check what you run now
nvm install 24.22.3     # or 22.23.5 / 26.13.1

In Docker, bump the base image tag (node:24.22.3-alpine) rather than relying on node:24 being rebuilt, and redeploy.

My read

The line I'd underline is the one the project repeats every time: "End-of-Life versions are always affected when a security release occurs." Node 20 and older got no fixes here. If something of yours still runs on 18 or 20, these HTTP/2 and TLS bugs are now public and will stay unpatched.

I covered the wider picture, including how to audit what versions you're running, in Node.js vulnerabilities in 2026.

More news