Node.js 11 End of Life
Support dates, vulnerabilities published since end of life, and upgrade guidance — rebuilt from live data.
Node.js 11 reached end of life on 30 Jun 2019. It no longer receives security fixes.
Support timeline
Official dates from the Node.js release process.
| Milestone | Date | Status |
|---|---|---|
| Initial release | 23 Oct 2018 | — |
| End of life | 30 Jun 2019 | 7.1 years ago |
| Active support ended | 1 Apr 2019 | security fixes only after this |
| Latest release | 11.15.0 · 30 Apr 2019 | final |
The cost of staying: CVEs since end of life
100 Node.js vulnerabilities have been published since 30 Jun 2019. All were fixed in supported branches — 11 received none of them. Source: NVD.
Node.js CVEs published since 11's EOL, by year
12 of the 100 are rated critical · data refreshed 2026-08-09
Published 20 Jan 2026 · rated critical — fixed in supported branches only, never in 11. Details
Published 7 Feb 2020 · rated critical — fixed in supported branches only, never in 11. Details
Published 7 Feb 2020 · rated critical — fixed in supported branches only, never in 11. Details
Where to go from 11
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 11 still safe to use?
No. Node.js 11 stopped receiving security fixes on 30 Jun 2019. Since then, 100 Node.js vulnerabilities have been published and fixed in supported branches — Node.js 11 received none of those fixes.
Can I still download Node.js 11?
Yes — the final release (11.15.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 11 to?
Upgrade to Node.js 26, the newest actively supported branch (supported until 30 Apr 2029).