惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

Recent Announcements
Recent Announcements
博客园 - Franky
博客园 - 三生石上(FineUI控件)
H
Hackread – Cybersecurity News, Data Breaches, AI and More
Apple Machine Learning Research
Apple Machine Learning Research
云风的 BLOG
云风的 BLOG
人人都是产品经理
人人都是产品经理
博客园 - 【当耐特】
L
LangChain Blog
Stack Overflow Blog
Stack Overflow Blog
H
Help Net Security
爱范儿
爱范儿
罗磊的独立博客
博客园_首页
美团技术团队
让小产品的独立变现更简单 - ezindie.com
让小产品的独立变现更简单 - ezindie.com
月光博客
月光博客
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
量子位
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
博客园 - 叶小钗
V
Visual Studio Blog
T
Tailwind CSS Blog

Node.js Blog

Node.js — Security Bug Bounty Program Paused Due to Loss of Funding Node.js — Node.js 25.9.0 (Current) Node.js — Developing a minimally HashDoS resistant, yet quickly reversible integer hash for V8 Node.js — Node.js 25.8.2 (Current) Node.js — Node.js 24.14.1 (LTS) Node.js — Node.js 22.22.2 (LTS) Node.js — Node.js 20.20.2 (LTS) Node.js — Tuesday, March 24, 2026 Security Releases Node.js — Node.js 25.8.1 (Current) Node.js — Evolving the Node.js Release Schedule Node.js — Node.js 22.22.1 (LTS) Node.js — Node.js 20.20.1 (LTS) Node.js — Node.js 25.8.0 (Current) Node.js — Node.js 25.7.0 (Current) Node.js — Node.js 24.14.0 (LTS) Node.js — New HackerOne Signal Requirement for Vulnerability Reports Node.js — Node.js 25.6.1 (Current) Node.js — Node.js 24.13.1 (LTS) Node.js — Node.js 25.6.0 (Current) Node.js — OpenSSL Security Advisory Assessment, January 2026 Node.js — Node.js 25.5.0 (Current) Node.js — Chalk to Node.js util styleText Node.js — Node.js 25.4.0 (Current) Node.js — Mitigating Denial-of-Service Vulnerability from Unrecoverable Stack Space Exhaustion for React, Next.js, and APM Users Node.js — Node.js 22.22.0 (LTS) Node.js — Node.js 25.3.0 (Current) Node.js — Node.js 24.13.0 (LTS) Node.js — Node.js 20.20.0 (LTS) Node.js — Tuesday, January 13, 2026 Security Releases Node.js — Node.js 24.12.0 (LTS)
Node.js — Upcoming CVE for End-of-Life Node.js Versions
2025-01-06 · via Node.js Blog

The Node.js Project

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:

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:

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.