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