What changed in the Node.js release lines
On October 28, 2026 the Node.js project shipped Node.js 26.13.0, and with it the 26.x line moved into Long Term Support under the codename Lithium. The release notes say the line will receive updates through the end of April 2029. Apart from metadata such as the process.release object, nothing changed compared with 26.12.1, so the switch itself carries no code risk.
The Node.js release schedule shows the moves around it. Node.js 24 (Krypton) entered Maintenance LTS on October 20, 2026 and reaches end of life on April 30, 2028. Node.js 22 (Jod) has been in maintenance since October 21, 2025 and reaches end of life on April 30, 2027. Those three are the only lines the schedule lists as supported, which leaves about five months for anything still running on 22.
The November 11 security release covers all three lines
Two weeks after the LTS switch, the project published security releases for every supported line on November 11, 2026: v22.23.5, v24.22.3 and v26.13.1. The highest severity on each line is high. Most of the fixes sit in HTTP/2 and TLS handling. Some examples from the advisory:
- A zero-length TLS write can make an HTTPS server copy its own heap into a request body. The advisory says this can leak TLS private keys and other users’ requests. It affects 22.x, 24.x and 26.x. Cleartext
node:httpis not affected. - TLS 1.2 renegotiation lets a client change its servername and bypass per-hostname client certificate checks, on all three lines.
- Several HTTP/2 crashes, leaks and use-after-free bugs, some reachable by an unauthenticated client.
- Proxy credentials can appear in
ERR_PROXY_INVALID_CONFIGerror messages, and so in logs and crash reports.
The advisory also states that end-of-life versions are always affected by a security release. A service still on Node.js 20 or older gets none of these fixes.
Where Node.js runs in a headless or integration stack
Node.js usually sits in more places than a team remembers. A Next.js or Remix storefront runs on it. So does the middleware that turns Shopify or BigCommerce orders into ERP sales orders, the webhook receiver for payment events, the overnight stock sync and the CI job that builds the theme. Each one can pin its own version in a Dockerfile, an .nvmrc file, a serverless runtime setting or a CI image, and they drift apart over time.
The November fixes matter most for services that terminate TLS or HTTP/2 inside Node.js itself. A webhook endpoint served directly with node:https, or a custom server that uses mutual TLS with an ERP or 3PL partner, is in scope for the certificate issues. When a load balancer or CDN terminates TLS in front of the app, exposure is lower. We would still patch, because the same image often gets reused for an internal service that is not behind the proxy.
The new release schedule from Node.js 27
Node.js 27 is the first line on a new schedule. According to the release working group, a new line now branches from main once a year in October and spends six months in an Alpha phase. The first build, 27.0.0-alpha.0.0.0, arrived on October 29, 2026. Alpha builds are signed, tagged and tested, but their API and ABI may change, and the project says they are meant for library authors and CI pipelines, not production. Node.js 27 is planned to become Current on April 22, 2027, LTS on October 20, 2027, and to reach end of life on April 30, 2030.
Two things change for planning. From 27 onward every line becomes LTS, so the old rule of skipping odd-numbered versions goes away. And lines from 27 have no Maintenance phase: they get 30 months of Active LTS, 36 months in total from the first Current release. Lines up to and including 26 keep the previous pattern of 12 months of active support followed by 18 months of maintenance. The schedule marks all of these dates as subject to change.
For a typical storefront or integration team we would move Node.js 22 services straight to 26 instead of stopping at 24. Node.js 24 is already in maintenance and its end of life comes a year earlier, so a stop at 24 means doing the work twice.





