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