Node.js released three security versions, 22.23.5, 24.22.3 and 26.13.1, on November 11, fixing 16 vulnerabilities: 7 high, 6 medium and 3 low, along with updates to three dependencies, llhttp, undici and sqlite. As always, the project reminds users that end-of-life versions (20 and older) are affected by every security release and will not be fixed.

The high-severity flaws that matter most for servers

  • CVE-2026-123864 (all three release lines): a re-entrancy flaw in HTTPS handling that lets an unauthenticated client read memory belonging to other connections; the project names TLS private keys and other users' requests as possible contents. It triggers when a handler calls res.flushHeaders() before the request body has ended and later calls res.end() with a non-empty chunk, and reading the leaked memory only takes any ordinary route that echoes or stores a request body. Cleartext node:http is not affected.
  • CVE-2026-123863 (24 and 26): on a default HTTP/2 server whose handler responds before the request body has ended, which is typical, any unauthenticated client can make the process fail an assertion and exit.
  • CVE-2026-123865 and CVE-2026-123866 (all three lines): the first permanently leaks the memory and file descriptors held by an HTTP/2 connection and triggers reliably against default servers; the second sends freed response memory to the peer when a stream is torn down, which can carry data from other connections.
  • CVE-2026-126051 (24 and 26): a TLS server that uses SNICallback, OCSPRequest, newSession, resumeSession or server.addContext() can be crashed remotely by an unauthenticated attacker.
  • The other two high-severity flaws are a servername change during TLS 1.2 renegotiation that bypasses per-hostname client certificate policies (CVE-2026-123872), and a use-after-free in respondWithFile() (CVE-2026-123874).

Apps behind nginx are at lower risk, but still need the update

Many Node apps on a VPS listen only locally over plain HTTP while nginx or Apache handles HTTPS and HTTP/2, a setup covered in hosting your first website with Nginx. In that case, the flaws above that only trigger when Node itself serves HTTPS or HTTP/2 do not apply. Two of the medium-severity flaws concern outgoing requests your app makes, though: proxy credentials disclosed in ERR_PROXY_INVALID_CONFIG error messages (CVE-2026-123871), and a certificate validation bypass in https.Agent through cross-policy TLS session reuse (CVE-2026-123877), so update anyway. The same week, Apache's HTTP/2 module also had a critical flaw; see that report.

How to update

  • Check your version with node -v; anything below 22.23.5, 24.22.3 or 26.13.1 needs updating.
  • Replacing the binary does not affect processes that are already running, so restart your app after the update; if PM2 manages it, run pm2 reload all, and PM2 usage is covered in deploying a Node.js app with PM2.
  • If you use Docker, rebuild on the new base image version and restart the container, as covered in our Docker primer.
  • Distribution packages will not help for now: Debian 12's 18.20.4 and Debian 13's 20.19.2 are both marked "vulnerable" on Debian's security tracker with no fix yet, and upstream stopped maintaining both versions long ago; Ubuntu's nodejs still showed "needs-triage" as of November 13. For apps that serve the public, move to a release line the project still maintains.