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