---
id: "VND-nodejs-upcoming-cve-for-eol-versions"
kind: "vulnerability"
aliases: []
title: "Node.js: Upcoming CVE for End-of-Life Node.js Versions"
severity: "low"
cvss: null
epss: null
exploited: false
status: "open"
category: "runtime"
products: [{"name": "node", "fixed": [], "affected": "", "ecosystem": "node"}]
ecosystems: ["node"]
tags: ["ci", "containers", "node", "node.js", "runtime", "self-hosted"]
not_affected_if: ["supported-release-line"]
published_at: "2025-01-06T16:00:00+00:00"
first_seen_at: "2026-10-23T19:13:00+00:00"
updated_at: "2026-10-25T05:39:32+00:00"
sources: [{"source": "nodejs", "url": "https://nodejs.org/en/blog/vulnerability/upcoming-cve-for-eol-versions", "first_seen_at": "2026-10-23T19:13:00+00:00"}]
---

# Node.js: Upcoming CVE for End-of-Life Node.js Versions

The Node.js project will issue a CVE identifier for end-of-life Node.js versions, citing CWE-1104 (use of unmaintained third-party components), to tell users those versions no longer receive security fixes. No new code flaw is described, so an attacker gains nothing new from this notice itself; the risk is running unpatched EOL releases.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- node:node affected ? fixed ?

## How to check

- Run `node -v` on each server, container and CI runner and compare against the supported lines listed in the notice (23 Current, 22 LTS, 20 and 18 Maintenance LTS).
- Run `npx is-my-node-vulnerable` to flag EOL versions or versions with an issued CVE.

## Fix

- Move any Node.js build that is not 23, 22, 20 or 18 to a supported release line, such as `22` (LTS), and retest.
- For EOL versions that must stay, the notice points to commercial support through the OpenJS Ecosystem Sustainability Program.

## Timeline

- 2026-10-23T19:13:00+00:00 nodejs https://nodejs.org/en/blog/vulnerability/upcoming-cve-for-eol-versions

## From the sources

Commercial support for versions past the Maintenance LTS phase is available through our OpenJS Ecosystem Sustainability Program partners Upcoming CVE for End-of-Life Node.js Versions TNJP The Node.js Project Upcoming CVE for End-of-Life Node.js Versions The Node.js Project is committed to ensuring the security and reliability of
applications built on Node.js. As part of this commitment, we regularly review
measures to help our users stay informed about security risks.
Announcement
We will soon issue a Common Vulnerabilities and Exposures (CVE) identifier for
End-of-Life (EOL) versions of Node.js. This CVE will serve as an official
notification to inform users that these versions are no longer maintained and
may pose significant security risks.
The CVE will cite Unsupported When Assigned under
CWE-1104 : Use of Unmaintained Third Party Components .
For more details on this decision, you can refer to the discussion in
this GitHub issue .
Why Issue a CVE?
Many organizations rely on CVE notifications to track security issues across
their software stacks. The Node.js project aims for a timely resolution and disclosure
for all reported vulnerabilities for the maintained release lines.
However, we do not issue CVEs for EOL release lines.
By issuing a CVE for EOL versions of Node.js, we aim to:
Raise Awareness: Inform users that running EOL versions exposes their
applications to potential vulnerabilities.
Encourage Upgrades: Prompt organizations and developers to update to
actively supported Node.js versions.
Improve Security: Reduce the number of applications running outdated and
unsupported versions of Node.js.
Node.js v16, despite being EOL for over a year, has still 11 million downloads per month.
What Does This Mean for You?
If you are using an EOL version of Node.js, we strongly encourage you to upgrade
to a supported version immediately. You can find the list of actively supported
versions and their maintenance schedules in the Node.js Release Schedule .
To check which version of Node.js your application is running, execute the
following command in your terminal:
node -v
You can also run is-my-node-vulnerable
to check if you are using an EOL version or any version with an CVE issued to it.
npx is-my-node-vulnerable
Supported Versions
As of the date of this announcement, the following versions are actively supported:
Node.js 23 (Current)
Node.js 22 (LTS)
Node.js 20 (Maintenance LTS)
Node.js 18 (Maintenance LTS)
All other versions are no longer supported and should be considered deprecated.
Questions and Feedback
We understand that upgrading may require effort, and we’re here to help. If you have
any questions or need assistance, please reach out to us via:
Node.js Help Repository
For organizations or developers who require continued use of EOL Node.js versions,
the OpenJS Ecosystem Sustainability Program
provides commercial support options.
Thank you for your attention to this important matter. Previous Tuesday, January 21, 2025 Security Releases Next Monday, July 8, 2024 Security Releases

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_