Node.js Security Release Patches 16 Flaws, Including a TLS Private Key Leak
Node.js shipped security releases for its 22.x, 24.x and 26.x lines on November 11, fixing 16 vulnerabilities, seven rated high. The headline bug can leak TLS private keys, and end-of-life versions get no fix at all.

Node.js shipped its November security release on November 11, 2026, fixing 16 vulnerabilities across every supported release line. The Node.js security release covers versions 22.23.5, 24.22.3 and 26.13.1, with seven flaws rated high, six medium and three low. The headline bug is a TLS flaw that can leak private keys to any visitor. If your server terminates TLS or speaks HTTP/2, this is an upgrade now situation, not an upgrade when convenient situation.
The release follows the project's fixed pattern. About a week ahead, on November 3, Node.js posted a pre-alert naming the date, the affected lines and the highest severity, with no details. The builds appeared on the afternoon of November 11, and the full advisory followed the same day. That gap between pre-alert and advisory is deliberate: it gives teams time to plan a deploy window without handing attackers the details first.
What the Node.js security release fixes
The advisory lists 16 CVEs. Seven are rated high, and most of them sit in HTTP/2 and TLS handling. The headline issue, CVE-2026-123864, is a TLS re-entrancy bug triggered by a zero-length TLS write. In plain terms, a client can send a specially crafted request that makes the server mishandle its own TLS state, and the failure can expose private key material. A private key leak is about as bad as a server bug gets: it undermines the encryption that the whole connection depends on.
The other high-severity bugs are mostly in HTTP/2: remote crashes, server memory sent to the peer, and a client-certificate bypass. A crash bug is a denial of service waiting to happen. Memory sent to the peer is an information leak. A client-certificate bypass breaks mutual TLS, the setup where the server checks who the client is, not just the other way around. None of these need a sophisticated attacker. They need a client that sends the wrong bytes.
The release also updates bundled dependencies. The llhttp HTTP parser goes to 9.4.4 on all three lines, SQLite to 3.54.1, undici to 7.30.2 on 24.x and 8.12.4 on 26.x, and Brotli to 1.2.1 on 24.x and 26.x. Those updates fix public vulnerabilities in the libraries Node.js ships with, which is why upgrading Node.js fixes more than the CVEs with Node.js names on them.
Who should move first
Move first if any Node process terminates TLS or serves HTTP/2 to untrusted clients. That is the directly exposed surface, and it is where the high-severity bugs live. Everyone on 22, 24 or 26 should upgrade, but the order matters: public-facing servers first, internal services second, build machines last.
If your app sits behind Nginx or a load balancer that terminates TLS, you have more breathing room, but not a free pass. Some of the fixes are on the client side, and your server still makes outbound TLS connections to databases, APIs and other services. Upgrade this week either way.
The hard line is end of life. Node.js 20 and Node.js 25 are end of life and get no fix. The advisory states plainly that end-of-life versions are always affected when a security release happens. If you are still on Node 20, there is no patched version to install. The fix is a major-version upgrade, and it should have happened months ago. Python 3.15 shipped with the same kind of deadline pressure, and the lesson is the same: running an unmaintained runtime is a decision, not an oversight.
The pattern to watch
This is Node.js's second security release in three weeks. The October 21 release fixed ten vulnerabilities, including a Brotli decoder bug, CVE-2026-111497, that Node.js said could lead to remote code execution when an app decompresses attacker-controlled data. Two security releases in three weeks is not a sign that Node.js is falling apart. It is a sign that the project is finding and fixing issues at a steady pace, and that the HTTP stack is getting the scrutiny it deserves.
The same week brought a separate Next.js security release, and the Node-RED remote code execution flaw showed what happens when the JavaScript ecosystem's plumbing gets exploited. The ecosystem is big enough now that a bug in one library ripples everywhere, and the release notes for this round credit Chris Rohlf, working with Claude and Anthropic Research, for five of the issues. AI-assisted security research is now finding the bugs, which is fitting, since AI-assisted coding is writing more of the code.
The advisory does not publish CVSS scores, only high, medium and low labels, and it does not say any of these flaws are being exploited. That is normal for Node.js. It also means the absence of an exploitation note is not a reason to wait. Exploitation reporting lags behind patching by weeks, and the details in the advisory are enough for an attacker to build a probe.
How to upgrade without breaking anything
Check your version first: node --version. Then check what line you are on and move to the patched version on that line: 22.23.5, 24.22.3 or 26.13.1. Do not jump lines to get the fix. A patch release is designed to be a drop-in replacement, and the NET 11 release showed the same discipline: patch on your line, upgrade lines on your own schedule.
Run your test suite after the upgrade, and smoke test the services that terminate TLS. The fixes touch HTTP/2 and TLS internals, so the things most likely to notice are connection handling and certificate checks. If you run Node behind a reverse proxy, test the proxy path too, since that is where the client-certificate logic lives.
Then set up the watcher. Node.js publishes pre-alerts about a week before each security release, and the release schedule is public. The teams that patch fast are not the ones that react fast. They are the ones that already know the date, have the deploy window booked, and treat the pre-alert as a calendar invite. The next one will come. It always does.


