Node.js end-of-life dates for every LTS line
Node.js 22 end of life is 30 April 2027, Node.js 24 ends on 30 April 2028 and Node.js 26, which becomes LTS on 28 October 2026, on 30 April 2029. Node.js 20 (30 April 2026), 18 (30 April 2025) and every older line have already ended. Dates checked against endoflife.date and the Node.js release schedule on 20 October 2026.
Node.js gives every new major release six months as Current. Up to Node.js 26, even-numbered majors then become LTS, which typically means 30 months of critical fixes (12 months Active LTS, then 18 months Maintenance), while odd-numbered majors end after their Current phase. From Node.js 27 the project ships one major a year, and every major becomes LTS.
- Latest release
- 26.13.1
- Supported lines
- 3
- End-of-life lines
- 23
- Next end of life
- 22 · 30 Apr 2027
Node.js 18 and 20 have ended
Upgrade, or keep 18 and 20 patched
Most applications should move to Node.js 24 or 26. When native modules, a vendor certification or a release freeze hold a service on 18 or 20, OSSeva ships patched, signed runtimes for those lines. The solution page lists what is covered and how the fix window works, and the upgrade guide covers the breaking changes.
Who patches Node.js after end of life
OSSeva provides Node.js extended support: patched, signed builds for Node.js 20, 18, 16 and 14 after upstream support ends, plus 24/7 operations on the Operate tier.
Node.js release timeline
All Node.js versions, release dates and end-of-life dates
| Version | Released | Active Support | Security Support | Latest | OSSeva |
|---|---|---|---|---|---|
| 26 (LTS) | 6 months ago(5 May 2026) | Ends in 11 months(27 Oct 2027) | Ends in 2 years and 5 months(30 Apr 2029) | 26.13.1 | – |
| 25 | 1 year and 1 month ago(15 Oct 2025) | Ended 8 months ago(1 Apr 2026) | Ended 6 months ago(1 Jun 2026) | 25.9.0 | – |
| 24 (LTS)Node.js 24 end of life | 1 year and 6 months ago(6 May 2025) | Ended 27 days ago(20 Oct 2026) | Ends in 1 year and 5 months(30 Apr 2028) | 24.22.3 | – |
| 23 | 2 years and 1 month ago(16 Oct 2024) | Ended 1 year and 8 months ago(1 Apr 2025) | Ended 1 year and 6 months ago(1 Jun 2025) | 23.11.1 | – |
| 22 (LTS)Node.js 22 end of life | 2 years and 7 months ago(24 Apr 2024) | Ended 1 year and 1 month ago(21 Oct 2025) | Ends in 5 months(30 Apr 2027) | 22.23.5 | – |
| 21 | 3 years and 1 month ago(17 Oct 2023) | Ended 2 years and 8 months ago(1 Apr 2024) | Ended 2 years and 6 months ago(1 Jun 2024) | 21.7.3 | – |
| 20 (LTS)Node.js 20 end of life | 3 years and 7 months ago(18 Apr 2023) | Ended 2 years and 1 month ago(22 Oct 2024) | Ended 7 months ago(30 Apr 2026) | 20.20.2 | Patched |
| 19 | 4 years and 1 month ago(18 Oct 2022) | Ended 3 years and 8 months ago(1 Apr 2023) | Ended 3 years and 6 months ago(1 Jun 2023) | 19.9.0 | – |
| 18 (LTS)Node.js 18 end of life | 4 years and 7 months ago(19 Apr 2022) | Ended 3 years and 1 month ago(18 Oct 2023) | Ended 1 year and 7 months ago(30 Apr 2025) | 18.20.8 | Patched |
| 17 | 5 years and 1 month ago(19 Oct 2021) | Ended 4 years and 8 months ago(1 Apr 2022) | Ended 4 years and 6 months ago(1 Jun 2022) | 17.9.1 | – |
| 16 (LTS)Node.js 16 end of life | 5 years and 7 months ago(20 Apr 2021) | Ended 4 years and 1 month ago(18 Oct 2022) | Ended 3 years and 2 months ago(11 Sept 2023) | 16.20.2 | Patched |
| 15 | 6 years and 1 month ago(20 Oct 2020) | Ended 5 years and 8 months ago(1 Apr 2021) | Ended 5 years and 6 months ago(1 Jun 2021) | 15.14.0 | – |
| 14 (LTS)Node.js 14 end of life | 6 years and 7 months ago(21 Apr 2020) | Ended 5 years and 1 month ago(19 Oct 2021) | Ended 3 years and 7 months ago(30 Apr 2023) | 14.21.3 | Patched |
| 13 | 7 years and 1 month ago(22 Oct 2019) | Ended 6 years and 8 months ago(1 Apr 2020) | Ended 6 years and 5 months ago(1 Jun 2020) | 13.14.0 | – |
| 12 (LTS) | 7 years and 7 months ago(23 Apr 2019) | Ended 6 years and 1 month ago(20 Oct 2020) | Ended 4 years and 7 months ago(30 Apr 2022) | 12.22.12 | – |
| 11 | 8 years and 1 month ago(23 Oct 2018) | Ended 7 years and 8 months ago(1 Apr 2019) | Ended 7 years and 5 months ago(30 Jun 2019) | 11.15.0 | – |
| 10 (LTS) | 8 years and 7 months ago(24 Apr 2018) | Ended 6 years and 6 months ago(19 May 2020) | Ended 5 years and 7 months ago(30 Apr 2021) | 10.24.1 | – |
| 9 | 9 years and 1 month ago(31 Oct 2017) | Ended 8 years and 5 months ago(30 Jun 2018) | Ended 8 years and 5 months ago(30 Jun 2018) | 9.11.2 | – |
| 8 (LTS) | 9 years and 6 months ago(30 May 2017) | Ended 7 years and 10 months ago(1 Jan 2019) | Ended 6 years and 11 months ago(31 Dec 2019) | 8.17.0 | – |
| 7 | 10 years and 1 month ago(25 Oct 2016) | Ended 9 years and 5 months ago(30 Jun 2017) | Ended 9 years and 5 months ago(30 Jun 2017) | 7.10.1 | – |
| 6 (LTS) | 10 years and 7 months ago(26 Apr 2016) | Ended 8 years and 7 months ago(30 Apr 2018) | Ended 7 years and 7 months ago(30 Apr 2019) | 6.17.1 | – |
| 5 | 11 years and 1 month ago(30 Oct 2015) | Ended 10 years and 5 months ago(30 Jun 2016) | Ended 10 years and 5 months ago(30 Jun 2016) | 5.12.0 | – |
| 4 (LTS) | 11 years and 2 months ago(9 Sept 2015) | Ended 9 years and 8 months ago(1 Apr 2017) | Ended 8 years and 7 months ago(30 Apr 2018) | 4.9.1 | – |
| 3 | 11 years and 3 months ago(4 Aug 2015) | Ended | Ended | 3.3.1 | – |
| 2 | 11 years and 6 months ago(4 May 2015) | Ended | Ended | 2.5.0 | – |
| 1 | 11 years and 10 months ago(20 Jan 2015) | Ended | Ended | 1.8.4 | – |
Lifecycle data from endoflife.date (MIT licence), refreshed 15 Nov 2026. Upstream policy: nodejs.org. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for.
What happens after Node.js end of life
The Node.js project ships no releases for a line once it reaches end of life, and each security announcement states that end-of-life versions are always affected. Node.js bundles its own OpenSSL, V8, undici and libuv, so an unpatched runtime carries unpatched copies of all of them regardless of what the host operating system has installed, and an OS-level package scan will not show it.
Official container images for an ended line also stop being rebuilt, so the Debian or Alpine layer under the runtime collects its own CVEs. Rebuilding on a maintained base clears most of that noise, but it does not replace the runtime's own fixes.
Security releases since Node.js 18 and 20 ended
Node.js 18 reached end of life on 30 April 2025 and Node.js 20 on 30 April 2026. Node.js 18 has missed 8 security releases and Node.js 20 has missed 4.
Eight Node.js security releases have shipped since 30 Apr 2025 and none included 18.x. The CVE directory lists 12 CVEs scored 7.0 or higher that those releases fixed. Counts as of 14 November 2026.
Node.js security releases since 30 Apr 2025, with the CVEs in the OSSeva CVE directory
| Release | Lines patched | Missed by | CVE | CVSS | Issue |
|---|---|---|---|---|---|
| 14 May 2025 | 20, 22, 23, 24 | 18 | CVE-2025-23166 | 7.5 | error handling in async cryptographic operations crashes the process |
| 15 Jul 2025 | 20, 22, 24 | 18 | CVE-2025-27210 | 7.5 | Windows device names bypass path traversal protection |
| 12 Jan 2026 | 20, 22, 24, 25 | 18 | CVE-2025-55130 | 9.1 | permission model bypass using crafted symlinks |
| 12 Jan 2026 | 20, 22, 24, 25 | 18 | CVE-2025-55131 | 7.1 | Buffer.alloc can return memory that is not zero-filled |
| 12 Jan 2026 | 20, 22, 24, 25 | 18 | CVE-2025-59465 | 7.5 | malformed HTTP/2 HEADERS frame crashes the process |
| 12 Jan 2026 | 20, 22, 24, 25 | 18 | CVE-2025-59466 | 7.5 | stack overflow errors become uncatchable with async_hooks |
| 12 Jan 2026 | 20, 22, 24, 25 | 18 | CVE-2026-21637 | 7.5 | exceptions in TLS PSK, ALPN and SNI callbacks crash the server |
| 24 Mar 2026 | 20, 22, 24, 25 | 18 | CVE-2026-21710 | 7.5 | __proto__ header name crashes servers that read req.headersDistinct |
| 17 Jun 2026 | 22, 24, 26 | 18 and 20 | CVE-2026-48933 | 7.5 | WebCrypto AES integer overflow crashes the process |
| 28 Jul 2026 | 22, 24, 26 | 18 and 20 | CVE-2026-56846 | 7.5 | retained HTTP/2 headers bypass maxSessionMemory |
| 28 Jul 2026 | 22, 24, 26 | 18 and 20 | CVE-2026-56848 | 7.5 | HTTP/2 re-entrant send causes heap use-after-free |
| 28 Jul 2026 | 22, 24, 26 | 18 and 20 | CVE-2026-58043 | 8.4 | permission model path matching over-grants file system access |
| 21 Oct 2026 | 22, 24, 26 | 18 and 20 | Not yet in the directory | n/a | 10 issues, 4 rated High by Node.js, listed in the October 2026 security releases announcement |
| 11 Nov 2026 | 22, 24, 26 | 18 and 20 | Not yet in the directory | n/a | 16 issues, 7 rated High by Node.js, listed in the November 2026 security releases announcement |
Release dates are from nodejs.org/dist/index.json and the lines patched from the Node.js security announcements. The directory lists Node.js CVEs matched at NVD to the product with a CVSS score of 7.0 or higher, so it is a subset of what each release fixed. The Node.js project does not assess ended lines: each announcement says end-of-life versions are always affected, so a scanner that follows those advisories can flag these CVEs against an ended line even though no fixed version of it exists.
Node.js upgrade paths
Node.js 22 ends on 30 April 2027, so it is a short stop for anyone moving off 18 or 20. Node.js 24 runs to 30 April 2028, and Node.js 26 becomes LTS on 28 October 2026 and runs to 30 April 2029. Native add-ons are compiled for one ABI version (115 on Node.js 20, 127 on 22 and 137 on 24), so each one has to be rebuilt for the new line, and an add-on that no longer builds is what usually pins a service to an old runtime.
| Route | It fits when | What drives the effort |
|---|---|---|
| Upgrade to Node.js 24 or 26 | The application can be retested on a new runtime before the next audit. | Native modules, deprecated APIs such as url.parse(), base images and test coverage. |
| Upgrade to Node.js 22 first | A smaller step is all the release window allows. | The same list, with fewer removed APIs. It ends on 30 April 2027, so the exercise repeats. |
| Stay on 18 or 20 with patched builds | A native dependency, a vendor certification or a release freeze blocks the move. | Nothing to migrate: it buys time and does not replace the upgrade. |
Running an end-of-life Node.js version?
OSSeva keeps end-of-life Node.js patched with signed builds and backported CVE fixes, documents it for your auditor, and can run it for you, so the upgrade happens on your schedule rather than the project’s.
Node.js extended supportIs Node.js 18 still supported?
No. Node.js 18 reached end of life on 30 April 2025 and 18.20.8 was its last release. The project has shipped 8 security releases since, and none included 18.x.
When is Node.js 22 end of life?
30 April 2027, according to the Node.js release schedule and endoflife.date. Node.js 22 has been in Maintenance LTS since 21 October 2025.
When does Node.js 24 reach end of life?
30 April 2028. Node.js 24 moved from Active LTS to Maintenance LTS on 20 October 2026. Node.js 26 becomes LTS on 28 October 2026 and ends on 30 April 2029.
Is Node.js 18 end of life?
Yes. Node.js 18 (Hydrogen) reached end of life on 30 April 2025, after its Active LTS and Maintenance phases, and 18.20.8 in March 2025 was its last release. The Node.js project ships no fixes for 18 now, so a vulnerability disclosed later stays unpatched upstream unless you move to a supported LTS line or use commercial support.
Is Node.js 20 end of life?
Yes. Node.js 20 (Iron) reached end of life on 30 April 2026, and 20.20.2 in March 2026 was its final release. Node.js 20 gets no more security releases from the project. Applications on it need to move to an LTS line that is still inside its window, which the table above shows with end dates.
How long is a Node.js LTS release supported?
About 30 months from the day it enters LTS. The Node.js release plan gives each LTS major 12 months of Active LTS, with fixes and audited updates, and then 18 months of Maintenance, which carries only critical bug fixes and security updates. Before Node.js 12 the split ran the other way: 18 months active, 12 months maintenance.
Which Node.js versions should I run in production?
Only Active LTS or Maintenance LTS releases, according to the Node.js project. Current releases exist so library authors can add support for a new major, and odd-numbered majors up to Node.js 26 never become LTS at all. The table above shows which LTS lines are still in support and the date each one ends.
What changes with Node.js 27?
Node.js 27 starts an annual release cycle. Up to Node.js 26 a new major shipped every six months and only even-numbered majors became LTS. From 27 onward there is one major a year, and every major moves to LTS after six months as Current, so the short-lived odd-numbered releases go away.
What is the latest Node.js version?
26.13.1, released 11 Nov 2026, on the 26 (LTS) line. Other supported lines: 24 and 22.
When is the next Node.js end of life?
Node.js 22 reaches the end of security support on 30 Apr 2027. After that date the project stops shipping security fixes for 22, and CVEs disclosed later stay unpatched upstream.
Which Node.js versions are still supported?
26 (until 30 Apr 2029), 24 (until 30 Apr 2028) and 22 (until 30 Apr 2027). Every other line has reached end of life, per the dates in the table above.
Can I get security patches for an end-of-life Node.js version?
Yes. OSSeva ships signed builds with backported CVE fixes for Node.js 20, 18, 16 and 14 after upstream support ends, on the Patch, Assure and Operate tiers, so you can stay on the version you run while you plan the upgrade.
Who provides Node.js support after end of life?
OSSeva provides Node.js extended support: patched, signed builds for Node.js 20, 18, 16 and 14 after upstream support ends, plus 24/7 operations on the Operate tier.
Get a quote
Still running an end-of-life Node.js?
Tell us the versions and the estate size. We will tell you whether to upgrade or keep it patched, and what each costs.
Prefer to talk or read more first?