Node.js · Lifecycle Status

Node.js End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Node.js versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Node.js 25 reaches end of life on June 1, 2026. Plan your migration now — 23 days remaining.
Latest Active
1.8.4
1 series
Next EOL
25
Jun 1, 2026
Active Versions
6
of 26 total
EOL Versions
19
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 201520162017201820192020202120222023202420252026202720281234567891011121314151617181920212223242526TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
1 1.8.4 Jan 20, 2015 Supported indefinitely Supported Active
2 2.5.0 May 4, 2015 Supported indefinitely Supported Active
3 3.3.1 Aug 4, 2015 Supported indefinitely Supported Active
4 LTS 4.9.1 Sep 9, 2015 Apr 30, 2018 2931 days past EOL EOL
5 5.12.0 Oct 30, 2015 Jun 30, 2016 3600 days past EOL EOL
6 LTS 6.17.1 Apr 26, 2016 Apr 30, 2019 2566 days past EOL EOL
7 7.10.1 Oct 25, 2016 Jun 30, 2017 3235 days past EOL EOL
8 LTS 8.17.0 May 30, 2017 Dec 31, 2019 2321 days past EOL EOL
9 9.11.2 Oct 31, 2017 Jun 30, 2018 2870 days past EOL EOL
10 LTS 10.24.1 Apr 24, 2018 Apr 30, 2021 1835 days past EOL EOL
11 11.15.0 Oct 23, 2018 Jun 30, 2019 2505 days past EOL EOL
12 LTS 12.22.12 Apr 23, 2019 Apr 30, 2022 1470 days past EOL EOL
13 13.14.0 Oct 22, 2019 Jun 1, 2020 2168 days past EOL EOL
14 LTS 14.21.3 Apr 21, 2020 Apr 30, 2023 1105 days past EOL EOL
15 15.14.0 Oct 20, 2020 Jun 1, 2021 1803 days past EOL EOL
16 LTS 16.20.2 Apr 20, 2021 Sep 11, 2023 971 days past EOL EOL
17 17.9.1 Oct 19, 2021 Jun 1, 2022 1438 days past EOL EOL
18 LTS 18.20.8 Apr 19, 2022 Apr 30, 2025 374 days past EOL EOL
19 19.9.0 Oct 18, 2022 Jun 1, 2023 1073 days past EOL EOL
20 LTS 20.20.2 Apr 18, 2023 Apr 30, 2026 9 days past EOL EOL
21 21.7.3 Oct 17, 2023 Jun 1, 2024 707 days past EOL EOL
22 LTS 22.22.2 Apr 24, 2024 Apr 30, 2027 356 days remaining Active
23 23.11.1 Oct 16, 2024 Jun 1, 2025 342 days past EOL EOL
24 LTS 24.15.0 May 6, 2025 Apr 30, 2028 722 days remaining Active
25 25.9.0 Oct 15, 2025 Jun 1, 2026 23 days remaining Warning
26 LTS 26.1.0 May 5, 2026 Already EOL Supported Active

What does Node.js end of life mean for your organization?

When a Node.js version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL Node.js should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Node.js versions. This is a bridge, not a permanent solution — plan your migration in parallel.

HeroDevs
Extended Node.js Support

Never-Ending Support for Node.js — security patches beyond EOL, drop-in replacement.

Learn More →
endoflife.ai
Check Your Full Stack

Upload your dependency file and scan your entire stack for EOL risk in seconds. Free, no account required.

Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Node.js?
The next Node.js version reaching EOL is 25 on June 1, 2026. See the full table above for all version EOL dates.
What is the latest supported version of Node.js?
The latest active version of Node.js is 1.8.4. Always verify against the table above as support windows can change.
What happens when Node.js reaches end of life?
When Node.js reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Node.js?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Node.js versions?
Yes — HeroDevs offers extended support for EOL Node.js versions, providing continued security patches while you plan your migration.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →