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