Node.js 13 End of Life
Support dates, vulnerabilities published since end of life, and upgrade guidance — rebuilt from live data.
Node.js 13 reached end of life on 1 Jun 2020. It no longer receives security fixes.
Support timeline
Official dates from the Node.js release process.
| Milestone | Date | Status |
|---|---|---|
| Initial release | 22 Oct 2019 | — |
| End of life | 1 Jun 2020 | 6.2 years ago |
| Active support ended | 1 Apr 2020 | security fixes only after this |
| Latest release | 13.14.0 · 29 Apr 2020 | final |
The cost of staying: CVEs since end of life
87 Node.js vulnerabilities have been published since 1 Jun 2020. All were fixed in supported branches — 13 received none of them. Source: NVD.
Node.js CVEs published since 13's EOL, by year
10 of the 87 are rated critical · data refreshed 2026-08-09
Published 20 Jan 2026 · rated critical — fixed in supported branches only, never in 13. Details
Published 16 Aug 2021 · rated critical — fixed in supported branches only, never in 13. Details
Published 7 Oct 2021 · rated critical — fixed in supported branches only, never in 13. Details
Where to go from 13
Recommended target: Node.js 26 (supported until 30 Apr 2029).
The newest actively supported branch is Node.js 26 (latest release 26.7.0). Review the Node.js changelog before upgrading. Run npx ls-engines to check package compatibility.
Frequently asked questions
Is Node.js 13 still safe to use?
No. Node.js 13 stopped receiving security fixes on 1 Jun 2020. Since then, 87 Node.js vulnerabilities have been published and fixed in supported branches — Node.js 13 received none of those fixes.
Can I still download Node.js 13?
Yes — the final release (13.14.0) 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 13 to?
Upgrade to Node.js 26, the newest actively supported branch (supported until 30 Apr 2029).