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.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 | 1.8.4 | Jan 20, 2015 | No EOL date | Supported | Active |
| 2 | 2.5.0 | May 4, 2015 | No EOL date | Supported | Active |
| 3 | 3.3.1 | Aug 4, 2015 | No EOL date | Supported | Active |
| 4 LTS | 4.9.1 | Sep 9, 2015 | Apr 30, 2018 | 2994 days past EOL | EOL |
| 5 | 5.12.0 | Oct 30, 2015 | Jun 30, 2016 | 3663 days past EOL | EOL |
| 6 LTS | 6.17.1 | Apr 26, 2016 | Apr 30, 2019 | 2629 days past EOL | EOL |
| 7 | 7.10.1 | Oct 25, 2016 | Jun 30, 2017 | 3298 days past EOL | EOL |
| 8 LTS | 8.17.0 | May 30, 2017 | Dec 31, 2019 | 2384 days past EOL | EOL |
| 9 | 9.11.2 | Oct 31, 2017 | Jun 30, 2018 | 2933 days past EOL | EOL |
| 10 LTS | 10.24.1 | Apr 24, 2018 | Apr 30, 2021 | 1898 days past EOL | EOL |
| 11 | 11.15.0 | Oct 23, 2018 | Jun 30, 2019 | 2568 days past EOL | EOL |
| 12 LTS | 12.22.12 | Apr 23, 2019 | Apr 30, 2022 | 1533 days past EOL | EOL |
| 13 | 13.14.0 | Oct 22, 2019 | Jun 1, 2020 | 2231 days past EOL | EOL |
| 14 LTS | 14.21.3 | Apr 21, 2020 | Apr 30, 2023 | 1168 days past EOL | EOL |
| 15 | 15.14.0 | Oct 20, 2020 | Jun 1, 2021 | 1866 days past EOL | EOL |
| 16 LTS | 16.20.2 | Apr 20, 2021 | Sep 11, 2023 | 1034 days past EOL | EOL |
| 17 | 17.9.1 | Oct 19, 2021 | Jun 1, 2022 | 1501 days past EOL | EOL |
| 18 LTS | 18.20.8 | Apr 19, 2022 | Apr 30, 2025 | 437 days past EOL | EOL |
| 19 | 19.9.0 | Oct 18, 2022 | Jun 1, 2023 | 1136 days past EOL | EOL |
| 20 LTS | 20.20.2 | Apr 18, 2023 | Apr 30, 2026 | 72 days past EOL | EOL |
| 21 | 21.7.3 | Oct 17, 2023 | Jun 1, 2024 | 770 days past EOL | EOL |
| 22 LTS | 22.23.1 | Apr 24, 2024 | Apr 30, 2027 | 293 days remaining | Active |
| 23 | 23.11.1 | Oct 16, 2024 | Jun 1, 2025 | 405 days past EOL | EOL |
| 24 LTS | 24.18.0 | May 6, 2025 | Apr 30, 2028 | 659 days remaining | Active |
| 25 | 25.9.0 | Oct 15, 2025 | Jun 1, 2026 | 40 days past EOL | EOL |
| 26 LTS | 26.5.0 | May 5, 2026 | Apr 30, 2029 | 1024 days remaining | Active |
What does Node.js end of life mean for your organization?
When a version of Node.js 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.
Node.js has 20 versions past end of life — security patches have stopped, but CVE disclosures haven't. Tell us what you run and we'll match you with a vetted extended-support provider within 1 business day. Free, no obligation.
Get My Support Options →