Node.js 22 · Version Status
Node.js 22 End of Life Date
Node.js 22 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 22 is actively supported. EOL date: April 30, 2027.
📅 Get reminded before Node.js 22 reaches EOL on April 30, 2027 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Apr 30, 2027
219 days remaining
Latest Release
22.23.2
LTS release
Release Date
Apr 24, 2024
Node.js 22 series
Lifecycle detail
Node.js 22 was released on April 24, 2024 and support is scheduled to end on April 30, 2027 — a planned supported lifespan of 3 years, in line with the 3 years median for Node.js LTS releases. It is a long-term support (LTS) release, so it carries a longer patch window than the interim releases around it. Its most recent patch is 22.23.2, published July 29, 2026.
Attack Surface
30/30 Critical tier
CISA KEV Exposure
0/20 Not in 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 22 end of life mean?
When Node.js 22 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 22 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 22 reach end of life?
Node.js 22 reached end of life on April 30, 2027. That is 219 days remaining.
Is Node.js 22 still supported?
Yes, Node.js 22 is currently supported. The EOL date is April 30, 2027.
What should I upgrade to from Node.js 22?
The recommended upgrade from Node.js 22 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 22 past EOL?
When Node.js 22 reaches end of life, the maintainers stop issuing 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.