Node.js 19 · Version Status
Node.js 19 End of Life Date
Node.js 19 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Node.js 19 is past end of life. This version no longer receives security patches. 1255 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 1, 2023
1255 days past EOL
Latest Release
19.9.0
Standard release
Release Date
Oct 18, 2022
Node.js 19 series
Where these dates come from
End of lifeJun 1, 2023Vendor's own page, read by our adapter · github.com · checked Nov 2, 2026high · 2 sources agree End of active supportApr 1, 2023Vendor's own page, read by our adapter · github.com · checked Nov 2, 2026high · 2 sources agree ReleaseOct 18, 2022Vendor's own page, read by our adapter · github.com · checked Nov 2, 2026high · 2 sources agree Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Node.js 19 was released on October 18, 2022 and support ended on June 1, 2023 — a supported lifespan of 8 months, shorter than the 2 years and 5 months median for Node.js releases. It was not an LTS release; Node.js reserves longer patch windows for its LTS releases. Its latest release on record is 19.9.0, published April 10, 2023 — 2 months before support ended. It has been past its end-of-life date for 3 years and 5 months. 6 newer Node.js releases have shipped since.
Attack Surface
30/30 Critical tier
CISA KEV Exposure
20/20 Named in 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 →
| Version | Latest | EOL Date | Status |
|---|
| 1 |
1.8.4 |
Supported |
EOL |
| 2 |
2.5.0 |
Supported |
EOL |
| 3 |
3.3.1 |
Supported |
EOL |
| 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 19 end of life mean?
When Node.js 19 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Node.js 19 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
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 19 reach end of life?
Node.js 19 reached end of life on June 1, 2023. This version is no longer receiving security patches.
Is Node.js 19 still supported?
No. Node.js 19 reached end of life on June 1, 2023 and is no longer receiving security patches.
What should I upgrade to from Node.js 19?
The recommended upgrade from Node.js 19 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 19 past EOL?
Since Node.js 19 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. 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.