Node.js 16 End of Life
Support dates, vulnerabilities published since end of life, and upgrade guidance — rebuilt from live data.
Node.js 16 reached end of life on 11 Sept 2023. It no longer receives security fixes.
Support timeline
Official dates, read directly from github.com and nodejs.org.
| Milestone | Date | Status |
|---|---|---|
| Initial release | 20 Apr 2021 | 5y 6mo ago |
| Active Support ended | 18 Oct 2022 | security fixes only after this |
| Security Support ended | 11 Sept 2023 | 3y 1mo ago |
| Latest release | 16.20.2 · 8 Aug 2023 | final |
The cost of staying: CVEs since end of life
47 Node.js vulnerabilities have been published since 11 Sept 2023. All were fixed in supported branches — 16 received none of them. Source: NVD.
Node.js CVEs published since 16's EOL, by year
6 of the 47 are rated critical · data refreshed 2026-10-05
Published 20 Jan 2026 · rated critical — fixed in supported branches only, never in 16. Details
Published 18 Oct 2023 · rated critical — fixed in supported branches only, never in 16. Details
Published 20 Feb 2024 · rated critical — fixed in supported branches only, never in 16. Details
Where to go from 16
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 16 still safe to use?
No. Node.js 16 stopped receiving security fixes on 11 Sept 2023. Since then, 47 Node.js vulnerabilities have been published and fixed in supported branches — Node.js 16 received none of those fixes.
Can I still download Node.js 16?
Yes — the final release (16.20.2) 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 16 to?
Upgrade to Node.js 27, the newest actively supported branch (supported until 30 Apr 2030).