Node.js 17 · Version Status

Node.js 17 End of Life Date

Node.js 17 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Node.js 17 is past end of life. This version no longer receives security patches. 1438 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 1, 2022
1438 days past EOL
Latest Release
17.9.1
Standard release
Release Date
Oct 19, 2021
Node.js 17 series
← Node.js 16 All Node.js versions Node.js 18 →
Recommended upgrade path
Node.js 26
Latest release: 26.1.0 · EOL: Supported
View full Node.js timeline →
HeroDevs
Extended Node.js 17 Support

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

Learn More →
All Node.js Versions
VersionLatestEOL DateStatus
1 1.8.4 Supported Active
2 2.5.0 Supported Active
3 3.3.1 Supported Active
4 LTS 4.9.1 Apr 30, 2018 EOL
5 5.12.0 Jun 30, 2016 EOL
6 LTS 6.17.1 Apr 30, 2019 EOL
7 7.10.1 Jun 30, 2017 EOL
8 LTS 8.17.0 Dec 31, 2019 EOL

What does Node.js 17 end of life mean?

When Node.js 17 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Node.js 17 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Node.js 26 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Node.js 17 reach end of life?
Node.js 17 reached end of life on June 1, 2022. This version is no longer receiving security patches.
Is Node.js 17 still supported?
No. Node.js 17 reached end of life on June 1, 2022 and is no longer receiving security patches.
What should I upgrade to from Node.js 17?
The recommended upgrade from Node.js 17 is Node.js 26 — the latest actively supported version. Check the Node.js full timeline for all supported versions.
What are the security risks of running Node.js 17 past EOL?
When Node.js 17 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Node.js should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →