Node.js 8 · Version Status
Node.js 8 End of Life Date
Node.js 8 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Node.js 8 is past end of life. This version no longer receives security patches. 2366 days past EOL — migrate to a supported version immediately.
EOL Date
Dec 31, 2019
2366 days past EOL
Latest Release
8.17.0
LTS release
Release Date
May 30, 2017
Node.js 8 series
Attack Surface
30/30 Critical tier
CISA KEV Exposure
20/20 Yes — CISA KEV
Extended Support
0/10 Available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
Extended Support
Extended Node.js 8 support is available
Commercial vendors offer security patches beyond EOL — compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| 1 |
1.8.4 |
Supported |
Active |
| 2 |
2.5.0 |
Supported |
Active |
| 3 |
3.3.1 |
Supported |
Active |
| 4 LTS |
4.9.1 |
Apr 30, 2018 |
EOL |
| 5 |
5.12.0 |
Jun 30, 2016 |
EOL |
| 6 LTS |
6.17.1 |
Apr 30, 2019 |
EOL |
| 7 |
7.10.1 |
Jun 30, 2017 |
EOL |
| → 8 LTS |
8.17.0 |
Dec 31, 2019 |
EOL |
What does Node.js 8 end of life mean?
When Node.js 8 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Node.js 8 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Node.js 26 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Node.js 8 reach end of life?
Node.js 8 reached end of life on December 31, 2019. This version is no longer receiving security patches.
Is Node.js 8 still supported?
No. Node.js 8 reached end of life on December 31, 2019 and is no longer receiving security patches.
What should I upgrade to from Node.js 8?
The recommended upgrade from Node.js 8 is
Node.js 26 — the latest actively supported version. Check the
Node.js full timeline for all supported versions.
What are the security risks of running Node.js 8 past EOL?
When Node.js 8 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Node.js should migrate immediately or implement compensating controls.
Does Node.js track end-of-life by point release (e.g. Node.js 26.1, Node.js 26.2)?
No — Node.js end-of-life dates apply to the entire 26.x release series, not individual point releases. A point release like Node.js 26.1 or Node.js 26.2 shares the same EOL date as Node.js 26. Security patches stop for the entire 26.x line on that date, regardless of which patch version you are running. Check the table above for EOL dates by major version series.