Node.js fixes 16 flaws, 7 rated high, in HTTP/2 and TLS: update to 26.13.1, 24.22.3 or 22.23.5
The Node.js project published its November 2026 security releases on 11 November: 26.13.1, 24.22.3 and 22.23.5. They fix 16 flaws, 7 of them rated high, mostly in HTTP/2 and TLS handling, including a way around client-certificate checks. The release post does not mention any attacks. What is known and what to do.
Updated 11 Nov 2026: see what changedHow urgent
Plan this week
Who is affected
Apps and servers that run Node.js 22.x, 24.x or 26.x below 22.23.5, 24.22.3 or 26.13.1, above all those that serve HTTP/2 or HTTPS directly from Node or check client certificates. Several flaws only touch 24.x and 26.x. We did not read each advisory in detail
What to do
Run node -v and update to 26.13.1, 24.22.3 or 22.23.5 (or later) this week; if you use client certificates (mTLS) or HTTP/2 straight from Node, do it first; move off end-of-life versions, which are always affected
Published 11 Nov 2026 · Sources last checked 11 Nov 2026No. 76 / 87
Updates, follow-ups and corrections
- Update · 11 Nov 2026. First version of the story, based on the Node.js project's own security release post (updated 11 Nov 2026) and its release listing, read in a browser. We did not read the individual CVE entries. The post does not mention attacks in the wild.
We keep the original text. When something changes, when we follow a story, or when we get something wrong, we add a dated note here instead of editing silently.
What happened
On 11 November 2026 the Node.js project released 26.13.1, 24.22.3 and 22.23.5, security releases for its three supported lines. According to its post they fix 16 vulnerabilitiesVulnerability A weakness in software, a setting or a process that an attacker could use to get in or do harm. Tap again to open the glossary: 7 high, 6 medium and 3 low. The release also updates bundled dependencies (llhttp, undici and sqlite). The post says the highest severity fixed is high on every line. It says nothing about attacks, known exploitsExploit A piece of code or a technique that takes advantage of a specific flaw to get something the attacker should not get. Tap again to open the glossary or a CISA listing at the time we read it. This follows the 21 October release, which fixed the Brotli flaw known as Node2Shell and was later listed by CISA as exploited.
What is in it, according to the post
The high-rated flaws, as the post labels them:
- HTTP/2: a remote abort of a session, a session leak after a protocol error during shutdown, freed memory sent to the other side when a stream is torn down, and a use-after-free when a file response is reset during a pending write. Some of these only affect 24.x and 26.x.
- HTTPSHTTPS The secure version of the web address protocol: it encrypts what travels between a visitor and your site and checks that the site is the real one. Tap again to open the glossary: writing a zero-length TLS record can re-enter the HTTP parser and read freed heap memory.
- TLS server: an uncaught exception from deferred handshake callbacks (24.x and 26.x).
- TLS 1.2 renegotiation: a change of server name can bypass client-certificate authentication on all three lines.
The medium and low ones include a second client-certificate bypass through a CA-only SNI override, a way to reuse TLS sessions across different certificate-validation policies in https.Agent, proxy credentials appearing in an error message, and two flaws in the permission model.
How serious it is
Seven high-rated flaws and a client-certificate bypass justify updating soon, but we have no report of attacks, so we put it at "week" and not "act". Whether you are exposed depends on what your app does: many of these need Node itself to serve HTTP/2 or HTTPS, or to check client certificates. An app that sits behind a proxy or a platform that ends TLS for you is less likely to be reachable, though the dependency updates still apply. That last point is our reasoning, not the post's.
What to do
- Check your version. Run
node -v, and look at the image or runtime your host uses. - Update to 26.13.1, 24.22.3 or 22.23.5 (or later) this week. Rebuild container images, since the version is baked in.
- Do it first if you use mTLS (client certificates) or serve HTTP/2 from Node. Those are the flaws that touch authentication and memory safety.
- Leave end-of-life versions behind. The post says they are always affected by a security release.
- Tell whoever runs your hosting if you do not control the Node version yourself.
What we could not confirm
We read the release post and the release listing, not each individual CVECVE A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug. Tap again to open the glossary entry, so we do not know exact exploit conditions or severity scores. The post gives no sign of exploitation, but that can change; we will add an update if it does. We did not test any of the fixes.
Watch the short video
The video loads from YouTube (privacy-enhanced mode) only when you press play.
Comments
No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.
We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.
Sources and verification
- Node.js, Wednesday, November 11, 2026 Security Releases (read 11 Nov 2026) (opens in a new tab)
- Node.js, release listing (read 11 Nov 2026) (opens in a new tab)
- Node.js, Wednesday, October 21, 2026 Security Releases (previous release, read earlier) (opens in a new tab)
We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.
Spotted a mistake? Email [email protected] and we will correct it and note the change.