Node.js · Lifecycle Status

Node.js End of Life (EOL) Dates & Support Timeline

Q: What is the end-of-life date for Node.js?

The next Node.js version reaching EOL is 22 on April 30, 2027. See the full table above for all version EOL dates.

Q: When is the Node.js support end date?

The next Node.js support end date is April 30, 2027, when version 22 reaches end of support. Each version has its own support end date — see the table above for every version's date.

Q: What is the latest supported version of Node.js?

The latest active version of Node.js is 26.3.1. Always verify against the table above as support windows can change.

Q: 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.

Complete end-of-life dates, support windows, and security status for all Node.js versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

📅 Get reminded before Node.js 22 reaches EOL on April 30, 2027 — alerts 90, 30 & 7 days out.

Google →

Latest Active

26.3.1

26 series

Next EOL

Apr 30, 2027

Active Versions

of 26 total

EOL Versions

no longer patched

High Risk

EOL Risk Score™ How is this calculated? →

EOL Recency

25/40

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 →

Release Cycle Timeline

■ EOL ■ Warning ■ Active ┊ Today

All Versions

Version	Latest Release	Release Date	EOL Date	Days	Status
1	1.8.4	Jan 20, 2015	No EOL date	Supported	Active
2	2.5.0	May 4, 2015	No EOL date	Supported	Active
3	3.3.1	Aug 4, 2015	No EOL date	Supported	Active
4 LTS	4.9.1	Sep 9, 2015	Apr 30, 2018	2976 days past EOL	EOL
5	5.12.0	Oct 30, 2015	Jun 30, 2016	3645 days past EOL	EOL
6 LTS	6.17.1	Apr 26, 2016	Apr 30, 2019	2611 days past EOL	EOL
7	7.10.1	Oct 25, 2016	Jun 30, 2017	3280 days past EOL	EOL
8 LTS	8.17.0	May 30, 2017	Dec 31, 2019	2366 days past EOL	EOL
9	9.11.2	Oct 31, 2017	Jun 30, 2018	2915 days past EOL	EOL
10 LTS	10.24.1	Apr 24, 2018	Apr 30, 2021	1880 days past EOL	EOL
11	11.15.0	Oct 23, 2018	Jun 30, 2019	2550 days past EOL	EOL
12 LTS	12.22.12	Apr 23, 2019	Apr 30, 2022	1515 days past EOL	EOL
13	13.14.0	Oct 22, 2019	Jun 1, 2020	2213 days past EOL	EOL
14 LTS	14.21.3	Apr 21, 2020	Apr 30, 2023	1150 days past EOL	EOL
15	15.14.0	Oct 20, 2020	Jun 1, 2021	1848 days past EOL	EOL
16 LTS	16.20.2	Apr 20, 2021	Sep 11, 2023	1016 days past EOL	EOL
17	17.9.1	Oct 19, 2021	Jun 1, 2022	1483 days past EOL	EOL
18 LTS	18.20.8	Apr 19, 2022	Apr 30, 2025	419 days past EOL	EOL
19	19.9.0	Oct 18, 2022	Jun 1, 2023	1118 days past EOL	EOL
20 LTS	20.20.2	Apr 18, 2023	Apr 30, 2026	54 days past EOL	EOL
21	21.7.3	Oct 17, 2023	Jun 1, 2024	752 days past EOL	EOL
22 LTS	22.23.0	Apr 24, 2024	Apr 30, 2027	311 days remaining	Active
23	23.11.1	Oct 16, 2024	Jun 1, 2025	387 days past EOL	EOL
24 LTS	24.17.0	May 6, 2025	Apr 30, 2028	677 days remaining	Active
25	25.9.0	Oct 15, 2025	Jun 1, 2026	22 days past EOL	EOL
26 LTS	26.3.1	May 5, 2026	Apr 30, 2029	1042 days remaining	Active

What does Node.js end of life mean for your organization?

When a version of Node.js reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL Node.js should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Node.js versions. This is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai

Need Extended Support?

We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.

Frequently Asked Questions

What is the end-of-life date for Node.js?

The next Node.js version reaching EOL is 22 on April 30, 2027. See the full table above for all version EOL dates.

When is the Node.js support end date?

The next Node.js support end date is April 30, 2027, when version 22 reaches end of support. Each version has its own support end date — see the table above for every version's date.

What is the latest supported version of Node.js?

The latest active version of Node.js is 26.3.1. Always verify against the table above as support windows can change.

What happens when Node.js reaches end of life?

When Node.js reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.

How do I check if I'm running an EOL version of Node.js?

Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.

Is there extended support available for EOL Node.js versions?

Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

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.

Deep Dive

Full Guide

Node.js EOL Master Guide — Official Schedule for Every Version

→

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →