Node 26 Goes LTS: Patch First, Upgrade Smart
On October 28, 2026, Node.js 26 becomes the long-term support release your production apps should run on. Five days earlier, a security release patched Node 22, 24 and 26 together. Here is the timeline, the fixes, and the safe upgrade order.
Amir Ali Liaqat · Founder & CEO, DesignsToDeploy

Every few years, the JavaScript runtime underneath most web backends quietly changes what teams should standardize on. This week is one of those moments, twice over. On October 21, 2026, the Node.js project shipped security releases for all three supported lines. On October 28, Node.js 26 moves from Current to Active LTS, becoming the fresh long-term support line. The two events belong together: patch what you run today, then plan the move to the line you will run for the next few years. This post explains both, in plain language, with the version numbers you actually need.
October 21: 10 fixes, 4 rated high
The October 21 security release fixed ten vulnerabilities across Node 22, 24 and 26, four of them rated high by the project. The headline flaw is CVE-2026-111497, an out-of-bounds write in the built-in Brotli decoder that the advisory describes as permitting remote code execution. Brotli is a compression format, so the flaw matters most for applications that decode compressed data they did not create. Three more high-severity flaws concern hostname handling: CVE-2026-105483 and CVE-2026-106069 describe TLS certificate hostname checks that could be bypassed with unusual IP address formats, and CVE-2026-105482 describes dns.resolve truncating names that contain a NUL character. The release also updated bundled components, Undici, c-ares, OpenSSL and SQLite, and removed trust tied to the compromised eMudhra intermediate certificate authority. The fixed versions are 22.23.4, 24.22.1 and 26.12.1. Node 20 and older lines are end of life and received no fix, which the advisory states plainly: end-of-life versions are always affected when a security release occurs.
October 28: the LTS timeline
LTS stands for long-term support. In practical terms, it is the project's promise to keep shipping critical and security fixes for a line for years, which is why production teams and procurement questionnaires care about it. Node 26 was first released as Current on May 5, 2026. It enters Active LTS on October 28, 2026, moves to Maintenance on October 20, 2027, and reaches end of life on April 30, 2029, according to the Node.js release schedule. Node 24, codenamed Krypton, moved from Active LTS to Maintenance on October 20, 2026, and is supported until April 30, 2028. Node 22, codenamed Jod, is in Maintenance LTS until April 30, 2027. That leaves a short, slightly awkward window between October 20 and October 28 in which no line is in Active LTS, and a clear answer after it: if your policy says Active LTS, Node 26 is the line from October 28. Node 26 is also the last line under the old release model: from Node 27 onward, the project plans one major release a year, with every line becoming LTS.
Upgrade without the surprises
The version bump itself is one line. Finding every Node your application actually runs is the real work, and it is where teams get caught out. Changing a default version with a version manager does not move a process manager entry that points at an old binary, a systemd unit with a hard-coded path, a cron job on another server, or a container image built months ago. The checklist is therefore: inventory every place Node runs, including servers, containers, CI images, process managers, scheduled jobs and serverless runtimes; move each supported line to its fixed release, 22.23.4, 24.22.1 or 26.12.1; restart the services and verify the version that is actually running, not the one on a developer laptop; rebuild container images from fresh base images and redeploy; and run tests, including a check that outbound TLS connections still validate correctly. One common trap deserves its own line: running npm audit checks your packages, not the Node.js runtime. A clean audit does not mean your runtime is patched. Only after the patched versions are confirmed everywhere should staging move to Node 26 LTS, and only after October 28, when the LTS promotion actually takes effect.
Why this matters for a business, not just developers
A runtime security release is easy to file under developer chores and forget. For a business, it is the layer every customer request passes through. Unpatched hostname checks weaken the trust that a connection really reaches the service it claims to reach. An unpatched decoder flaw in a server that accepts compressed input is a door nobody wants open. And running an end-of-life runtime means the next security release, whenever it lands, will not help at all. The cost of patching is a planned maintenance window. The cost of not patching is explaining, after the fact, why a known fix sat unapplied. At DesignsToDeploy, we treat runtime maintenance as part of delivering software, not an extra: our Node.js and Express backends are built and deployed with the same discipline we recommend here, patched lines, verified running versions, and a named LTS target for every project.
Our take
Patch first, upgrade second, verify always. This week gives teams a clean order of operations: apply the October 21 fixes to the line you run today, confirm the running version changed everywhere it matters, and then standardize new and staging work on Node 26 LTS from October 28. If you are still on Node 20 or older, treat migration as the project, not the patch, because no patch is coming for that line. If you need help auditing which Node versions your product actually runs, or moving a production backend to a supported LTS line without downtime, that is exactly the kind of backend work DesignsToDeploy does every week.
1 / 5Keep reading

Git 2.56: Safer Conflicts, a Tidier Repo, and Much Faster History
Git 2.56 landed in late September 2026 with one theme: stop the small mistakes that cost teams hours. Here is what changed, from git add --resolved and branch cleanup to merge-base speedups that turn minutes into milliseconds.
Read article
VS Code 1.145: Coding Agents That Work While You Sleep
VS Code 1.145 shipped November 4, 2026, turning the editor into an agent host: remote agents you can preview in the Agents window, automations on a five-field cron schedule, and nested sessions that mix harnesses. What changed, what is still preview, and the four moves to set it up today.
Read article
GitHub Copilot Now Works in Xcode and JetBrains Air
On November 3 and 4, 2026, GitHub put Copilot inside Xcode's built-in coding assistant and JetBrains Air. One subscription now works across the IDEs developers already use, with cloud tasks in isolated sandboxes and no new JetBrains subscription required. What changed, what it costs, and the three moves to try it this week.
Read article