Node.js November 2026 Security Update: What to Patch Now
Node.js shipped November 2026 security releases patching 16 CVEs, seven High severity, across the 22.x, 24.x and 26.x lines. Here is what changed and how to update.
Node.js shipped its November 2026 security releases on Wednesday, November 11, patching 16 separate vulnerabilities — seven of them rated High severity — across all three currently active release lines. If you run Node.js 22.x, 24.x, or 26.x in production, the short version is: update to 22.23.5, 24.22.3, or 26.13.1 respectively, and do it soon, because several of the High-severity issues can be triggered remotely by an unauthenticated client over plain HTTP/2 or TLS.
- What: 16 CVEs fixed across Node.js 22.x, 24.x and 26.x (7 High, 6 Medium, 3 Low severity)
- When: Released Wednesday, November 11, 2026
- Patched to: v22.23.5 / v24.22.3 / v26.13.1
- Highest severity: High, on every active release line
- Heads up: a pre-alert went out to the oss-security mailing list on November 4, flagging the High rating a week before any technical detail was published
What happened
The Node.js project runs a documented security-release process: when a fix is severe enough to warrant coordinated disclosure, the team posts a brief "pre-alert" to the oss-security mailing list days ahead of the actual release, naming the affected lines and the worst severity rating involved, but withholding CVE numbers and technical details until the patched builds are ready. That pre-alert went out on November 4, 2026, stating that new versions of the 22, 24 and 26 release lines were coming "on or shortly after" November 11, and that the highest-severity issue being fixed was rated High.
The releases arrived on schedule. Node.js's own advisory, published on nodejs.org, lists 16 vulnerabilities fixed across the three lines, plus routine dependency bumps to llhttp, undici and the bundled SQLite build. It's also the project's second security-release cycle in three weeks: the previous one shipped on October 21, 2026. Back-to-back cycles that close together are a reminder that patch cadence for a runtime this central to the web doesn't slow down just because your team is busy with something else.
Am I affected?
If your deployment runs any build of Node.js 22, 24 or 26 older than the versions below, yes. Because the project's security-release policy treats end-of-life lines as "always affected when a security release occurs" without producing a fix for them, anyone still running an EOL line (18.x, 20.x, 23.x, 25.x and earlier, all of which have already reached end of life) should treat this as a prompt to finally move to a maintained line, not just to patch.
Not every one of the 16 bugs hits every line. Five of them — including the two most severe HTTP/2 teardown issues — only affect 24.x and 26.x, because the vulnerable code paths were introduced after 22.x's HTTP/2 implementation diverged. The other eleven, including the TLS renegotiation and certificate-validation bugs, affect all three lines. The practical upshot is the same regardless: every active line has at least one High-severity fix, so there's no line where you can skip the update.
| Release line | Patched version | Highest severity fixed | CVEs addressed |
|---|---|---|---|
| 22.x (LTS "Jod") | v22.23.5 | High | 11 of 16 |
| 24.x (LTS "Krypton") | v24.22.3 | High | 16 of 16 |
| 26.x (LTS "Lithium") | v26.13.1 | High | 16 of 16 |
The seven High-severity issues
Most of the High-severity fixes cluster around two subsystems: HTTP/2 session teardown and TLS. In short, several of these let an unauthenticated remote client crash a Node.js process, and one lets a client read memory it shouldn't be able to see:
- HTTP/2 remote-abort via a reachable assertion. A client can trigger an internal assertion failure during HTTP/2 session teardown and crash the server, over both TLS and cleartext connections, on 24.x and 26.x.
- A TLS re-entrancy bug that leaks memory across connections. A zero-length TLS write can re-enter the HTTP parser in a way that causes the server to copy its own heap — potentially including other connections' data — into the response body. This affects all three lines and is the one issue in this batch with a confidentiality impact, not just a crash.
- Two more HTTP/2 teardown bugs that let a protocol error during shutdown either prevent a session from ever being cleaned up (a slow resource leak) or free response memory that then gets sent to a peer (a use-after-free), both across all three lines.
- A deferred-callback use-after-destroy in TLS server handshakes that lets a remote client terminate the server process, on 24.x and 26.x.
- A TLS 1.2 renegotiation bug that lets a client change the SNI servername mid-handshake, bypassing client-certificate authorization checks tied to the original hostname, on all three lines.
- A use-after-free when a
respondWithFile()stream is reset mid-write, letting a client corrupt server memory on 24.x and 26.x.
None of these require authentication; several are reachable with nothing more than a standard HTTP/2 or TLS connection to a default server configuration, which is exactly why "update soon" rather than "update whenever" is the right posture here.
The medium- and low-severity fixes
The six Medium-severity issues are a mix of a one-byte heap buffer overflow in HTTP/2's Alt-Svc handling, a mutual-TLS bypass where a client authorized for the default hostname can reach a differently-protected hostname, an HTTP/2 memory-exhaustion path where inbound data queued on an undrained stream isn't counted against maxSessionMemory, a proxy-credential disclosure bug in error messages (a follow-up to an earlier, incompletely-fixed CVE), a certificate-validation bypass in https.Agent session reuse across different TLS policies, and a NULL-pointer crash when a client cancels a file download mid-stream.
The three Low-severity issues are a Permission Model bypass that can leak the names of files a process isn't allowed to read via recursive fs.watch() on macOS and Windows, an uncatchable exception in the zlib streaming API if a peer disconnects mid-compression, and a Permission Model over-grant where a wildcard --allow-fs-read/--allow-fs-write rule can match more paths than intended. All three affect every active release line.
Why this release leans so heavily on HTTP/2 and TLS
Ten of the sixteen fixes in this release touch either the HTTP/2 implementation or the TLS stack — the two subsystems that sit directly on the network boundary, parsing untrusted input from clients before any application code runs. That's a pattern worth knowing if you're deciding how urgently to act: a bug in, say, the Permission Model needs a specific flag enabled to matter, but a crash reachable over a plain HTTP/2 connection is live the moment your server accepts traffic. Anyone running Node.js as an HTTP/2 or TLS-terminating edge — including services built on protocols that ride on top of HTTP/2, like gRPC — should read the HTTP/2-related entries first.
Dependency bumps included in this release
Beyond the 16 numbered CVEs, the advisory also bundles version bumps for three dependencies Node.js ships internally: llhttp, the HTTP parser, updated across all three lines (22.x, 24.x and 26.x); undici, the built-in HTTP client, updated on 24.x and 26.x; and the bundled build of SQLite that backs the node:sqlite module, updated on 22.x and 24.x. Node.js's advisory doesn't attach separate CVE numbers to these three bumps, so they read as routine hardening and upstream bug-fix pulls rather than standalone vulnerabilities — but they still land in your dependency tree the moment you take the update, which matters if your organization tracks SBOM changes release over release.
What the November 4 pre-alert did and didn't tell you
Node.js's security-release process is deliberately staged: the pre-alert exists so operators can schedule a maintenance window before the technical details — and therefore the exploit details — become public. The November 4 message to oss-security, from Node.js contributor Antoine du Hamel, said only that new 22.x, 24.x and 26.x builds were coming on or shortly after November 11, and that the worst issue being fixed was High severity. It named no CVEs, gave no counts, and described no vulnerable code paths. A short follow-up on November 11 confirmed the releases had shipped and pointed to the official advisory for the real detail. That gap between "something High severity is coming" and "here's exactly what it is" is standard practice for the project, and it's why teams that track these pre-alerts can plan an update window in advance instead of reacting cold.
How to update Node.js right now
The patched builds are live on nodejs.org's download page and in the usual package repositories. If you manage versions with a version manager, the update is typically one of:
nvm install 22.23.5 && nvm alias default 22.23.5(or the 24.22.3 / 26.13.1 equivalent for your line)fnm install 24.22.3if you use fnm- Pulling the updated
node:22,node:24ornode:26base image if you deploy via Docker — rebuild and redeploy rather than relying on an image that was pulled before November 11 - Your OS package manager's update command, if you installed Node.js from a distro or NodeSource repository
After updating, run node -v to confirm you're on 22.23.5, 24.22.3 or 26.13.1 (or later) before considering the job done. The individual release notes for v22.23.5, v24.22.3 and v26.13.1 on GitHub list the exact commits behind each fix, if you need that level of detail for a change-management record.
Can't update immediately?
If you can't patch right away — a staged rollout, a frozen deployment window, a dependency that pins an older Node.js build — there's no official workaround for most of these issues; they're fixed in the runtime itself, not through a configuration flag. A few partial mitigations are worth knowing about in the meantime: the TLS renegotiation and mTLS-bypass issues only matter if you rely on client-certificate authentication tied to hostname, so services that don't use mTLS are not exposed to those two specific bugs. The Permission Model issues only matter if you've enabled the Permission Model (--permission) in the first place. None of that is a substitute for updating — it's only useful for triaging which fixes are most urgent for your specific setup while you schedule the real update.
What about end-of-life Node.js versions?
If you're running a line that's already past end of life, Node.js's own advisory is explicit that EOL versions are considered affected whenever a security release happens — there's just no patch coming for them, because the project has stopped maintaining them. That's not a new warning specific to this release; it's the standing consequence of staying on an unsupported line. If your deployment hasn't been through an upgrade pass since an older LTS line expired, this is as good a prompt as any to plan the move, the same way a shift to a newer, actively maintained runtime made sense when .NET 11 replaced older .NET LTS lines on that stack.
What next
Treat this like any other runtime security release that lands with multiple unauthenticated-remote, High-severity bugs in network-facing code: don't wait for the next scheduled deploy. Update to 22.23.5, 24.22.3 or 26.13.1 depending on your line, verify the version string after deploying, and check whether your base container images or CI pipelines are pinned to an older patch version that needs bumping too. Node.js's release schedule and current end-of-life dates for every line are maintained on the project's release page, which is worth bookmarking if you're responsible for keeping a fleet of services on supported versions.
Frequently asked questions
Which Node.js versions fix the November 2026 vulnerabilities?
Node.js 22.23.5, 24.22.3 and 26.13.1, all released Wednesday, November 11, 2026, patch the vulnerabilities fixed in this cycle for the 22.x, 24.x and 26.x lines respectively.
How many vulnerabilities were fixed and how severe are they?
16 CVEs in total: seven rated High severity, six Medium, and three Low. Every active release line has at least one High-severity fix.
Do all three release lines have the same vulnerabilities?
No. Eleven of the 16 CVEs affect 22.x, 24.x and 26.x alike. The other five, mostly newer HTTP/2 session-teardown issues, only affect 24.x and 26.x.
What was the November 4 pre-alert about?
Node.js posted a pre-alert to the oss-security mailing list on November 4, 2026, stating that new 22.x, 24.x and 26.x builds were coming on or shortly after November 11 with a High-severity fix included, without naming any CVEs or technical details.
Am I still affected if I'm on an end-of-life Node.js version?
Yes. Node.js's advisory states that end-of-life versions are considered affected whenever a security release occurs, even though no patch is produced for them.
How do I check which Node.js version I'm running?
Run node -v in a terminal and compare the result against 22.23.5, 24.22.3 or 26.13.1 (or later) for your release line.
Sources
- Node.js: November 2026 Security Releases (official advisory)nodejs.org
- GitHub: Node.js v22.23.5 release notesgithub.com
- GitHub: Node.js v24.22.3 release notesgithub.com
- GitHub: Node.js v26.13.1 release notesgithub.com
- Node.js downloadsnodejs.org
- Node.js release schedule and end-of-life datesnodejs.org
Felix Moreau writes Pandromeda's software coverage and how-to guides. He covers Windows, macOS and Linux updates, the apps people rely on, emulators and developer tools, and turns official documentation into clear, numbered steps that work on the current version.


