Node.js 17 End of Life
Support dates, vulnerabilities published since end of life, and upgrade guidance — rebuilt from live data.
Node.js 17 reached end of life on 1 Jun 2022. It no longer receives security fixes.
Support timeline
Official dates, read directly from github.com and nodejs.org.
| Milestone | Date | Status |
|---|---|---|
| Initial release | 19 Oct 2021 | 5y ago |
| Active Support ended | 1 Apr 2022 | security fixes only after this |
| Security Support ended | 1 Jun 2022 | 4y 4mo ago |
| Latest release | 17.9.1 · 1 Jun 2022 | final |
The cost of staying: CVEs since end of life
70 Node.js vulnerabilities have been published since 1 Jun 2022. All were fixed in supported branches — 17 received none of them. Source: NVD.
Node.js CVEs published since 17's EOL, by year
8 of the 70 are rated critical · data refreshed 2026-10-05
Published 20 Jan 2026 · rated critical — fixed in supported branches only, never in 17. Details
Published 21 Aug 2023 · rated critical — fixed in supported branches only, never in 17. Details
Published 18 Oct 2023 · rated critical — fixed in supported branches only, never in 17. Details
Where to go from 17
Recommended target: Node.js 27 (supported until 30 Apr 2030).
The newest actively supported branch is Node.js 27 (latest release ). Review the Node.js changelog before upgrading. Run npx ls-engines to check package compatibility.
Frequently asked questions
Is Node.js 17 still safe to use?
No. Node.js 17 stopped receiving security fixes on 1 Jun 2022. Since then, 70 Node.js vulnerabilities have been published and fixed in supported branches — Node.js 17 received none of those fixes.
Can I still download Node.js 17?
Yes — the final release (17.9.1) generally remains available from vendor archives and OS package mirrors, but installing it means running software with known, unpatched vulnerabilities.
What should I upgrade Node.js 17 to?
Upgrade to Node.js 27, the newest actively supported branch (supported until 30 Apr 2030).