Node.js — End-Of-Life Skip to content LearnAboutDownloadBlogDocsBeta DocsContributeCourses Start typing... ⌘ K Change pageEnd-Of-LifeAbout Node.jsAbout Node.js® Node.js Releases Security Reporting Project Governance Partners & Supporters Branding of Node.js End-of-Life (EOL) Get InvolvedGet Involved Collaboration Summit Upcoming Events Contribute to Node.js Code of Conduct End-Of-Life (EOL) Why and how Node.js releases reach End-Of-Life Major versions of Node.js are released, patched, and designated End-Of-Life on a predictable schedule. As it's not feasible to maintain all release lines in perpetuity, after a planned maintenance period, a Node.js major release line will stop being maintained by the project. Upgrade to the latest LTS Node.js®orGet security support for EOL versions View the Node.js release schedule. What Happens When a Release Line Reaches EOL When a version reaches End-Of-Life, it means that it will no longer receive updates, including security patches. This can leave applications running on these versions vulnerable to security issues and bugs that will never be fixed. No more vulnerability fixes: When new security releases reveal issues and patches in newer major lines, even if the same vulnerability affects EOL release lines, there will not be any new releases for them. Users still clinging on to EOL release lines and using affected code paths will be immediately vulnerable to attacks exploiting these disclosed vulnerabilities. Tool-chain breakage: EOL releases may no longer dynamically link to newer versions of the shared libraries they depend on, blocking or breaking system updates. Ecosystem drift: Many popular user-land packages drop support for EOL Node.js releases over time. When an application clings onto outdated packages, it may suffer from even more unfixed vulnerabilities and bugs, further drifting away from ecosystem norm. Compliance red flags: Many industry audits forbid unmaintained runtimes. EOL Versions Hide non-LTS versions Version (Codename) Last updated Vulnerabilities Details v25 Mar 31, 2026 5High7Medium3Low Details v23 May 14, 2025 2High2Medium Details v21 Apr 10, 2024 7High5Medium Details v20 (Iron) Mar 24, 2026 27High24Medium9Low Details v19 Apr 10, 2023 1High3Medium2Low Details v18 (Hydrogen) Mar 27, 2025 15High19Medium4Low Details v17 Jun 01, 2022 1High3Medium1Low Details v16 (Gallium) Aug 08, 2023 11High18Medium4Low Details v15 Apr 06, 2021 1Critical6High1Medium1Low Details v14 (Fermium) Feb 16, 2023 2Critical16High16Medium5Low Details v13 Apr 29, 2020 1Critical2High Details v12 (Erbium) Apr 05, 2022 2Critical13High6Medium3Low Details v11 Apr 30, 2019 3High1Medium Details v10 (Dubnium) Apr 06, 2021 1Critical12High3Medium1Low Details v9 Jun 12, 2018 1Critical4High1Medium1Low Details v8 (Carbon) Dec 17, 2019 1Critical11High2Medium1Low Details v7 Jul 11, 2017 3High2Medium Details v6 (Boron) Apr 03, 2019 16High12Medium Details v5 Jun 23, 2016 15High8Medium Details v4 (Argon) Mar 29, 2018 2Critical17High9Medium Details v0 Feb 22, 2017 2Critical Details Commercial Support Despite the obvious downsides of using EOL releases, in practice, organizations face constraints that prevent immediate upgrades, such as legacy codebases, compliance requirements, or complex dependency chains. Through the OpenJS Foundation Ecosystem Sustainability Program, Node.js is supported by HeroDevs, NodeSource, and TuxCare to provide commercial services for security fixes. HeroDevs provides Never-Ending Support (NES) for Node.js versions past their official maintenance phase. This includes security patches, compliance assistance, and technical support to help bridge the gap while you plan your upgrade strategy. NodeSource offers commercial-grade upgrade assessments and expert support to safely modernize Node.js applications still running on EOL versions. Their guided Upgrade Program delivers in-depth risk analysis, identifies migration blockers, and provides a custom roadmap to streamline your upgrade journey. TuxCare’s Endless Lifecycle Support (ELS) gives you continued security patching for end-of-life Node.js versions. Security fixes are backported from upstream, tested for integrity and regression, signed, SLA-backed, and delivered through your existing package managers. Using EOL releases through commercial support should be viewed as a temporary solution—the goal should always be to upgrade to actively supported versions. Reading Time 2 min Contribute Edit this page Table of Contents Why and how Node.js releases reach End-Of-Life What Happens When a Release Line Reaches EOL EOL Versions Commercial Support About Node.js End-of-Life (EOL) v24.19.0Latest LTSv26.7.0Latest Release Copyright OpenJS Foundation and Node.js contributors. All rights reserved. The OpenJS Foundation has registered trademarks and uses trademarks. For a list of trademarks of the OpenJS Foundation, please see our Trademark Policy and Trademark List. Trademarks and logos not indicated on the list of OpenJS Foundation trademarks are trademarks™ or registered® trademarks of their respective holders. Use of them does not imply any affiliation with or endorsement by them. OpenJS FoundationAI Coding Assistants PolicyBylawsCode of ConductCookie PolicyPrivacy PolicySecurity PolicyTerms of UseTrademark ListTrademark Policy