Tech

Explainer

Updated

Is Node.js 20 still supported?

Key facts

The last Node.js 20 release, 20.20.2, was a security release dated 2026-03-24, and the LTS lines now listed are v22, v24 and v26.

No, Node.js 20 has reached end-of-life, and the Node.js releases page lists v20 (Iron) with the status EOL. The end-of-life page says that "When a version reaches End-Of-Life, it means that it will no longer receive updates, including security patches." The last Node.js 20 release, 20.20.2, is dated 2026-03-24.

Node.js release lines from v20 to v27

The table copies the rows for v20 to v27 from the releases page as read on 2026-11-18. Each row gives the line's codename, its first release date, its status and the Last updated date the page shows.

LineFirst releasedStatus, last updated
v27Oct 29, 2026Alpha, Nov 16, 2026
v26 LithiumMay 05, 2026LTS, Nov 10, 2026
v25Oct 15, 2025EOL, Mar 31, 2026
v24 KryptonMay 06, 2025LTS, Nov 10, 2026
v23Oct 16, 2024EOL, May 14, 2025
v22 JodApr 24, 2024LTS, Nov 11, 2026
v21Oct 17, 2023EOL, Apr 10, 2024
v20 IronApr 17, 2023EOL, Mar 24, 2026

Node.js 22 is the oldest line the table still marks LTS, and its status has its own page at Is Node.js 22 still supported?

What changed and when

The releases page gives Apr 17, 2023 as the first release date of Node.js 20 and Mar 24, 2026 as its Last updated date. The page labels that column Last updated, not end-of-life date.

The release post for Node.js 20.20.2 (LTS) is dated 2026-03-24, the same day as that Last updated date, and reads "This is a security release." Its notable changes list fixes for seven CVEs, including fixes to TLS and the permission model.

The end-of-life page now lists v20 (Iron) among its EOL versions with a Last updated date of Mar 24, 2026. Its Vulnerabilities column gives v20 counts of 27 high, 24 medium and 9 low, the largest high count of any line in that table.

The release pattern has also changed since Node.js 20 came out. The releases page says that up to Node.js 26, odd-numbered releases became unsupported after six months and even-numbered releases moved to Active LTS. It says that starting with Node.js 27, the release cycle will be annual, and every major version will move to LTS status after six months in Current and six more months in Alpha. The table lists v27 with the status Alpha.

Node.js 18, the LTS line before 20, also carries the status EOL, and its page is at Is Node.js 18 still supported?

Edge cases a reader meets next

  • Where to move from Node.js 20. The releases page says that "Production applications should only use Active LTS or Maintenance LTS releases." The lines it marks LTS are v22 (Jod), v24 (Krypton) and v26 (Lithium), and it names v26.13.1 as the Latest LTS release.
  • An EOL line gets no patches from the project. The end-of-life page says that when security releases patch newer major lines, EOL lines get no new release, even when the same vulnerability affects them.
  • Other costs of staying. The same page says EOL releases may stop linking to newer versions of the shared libraries they depend on, that many packages drop support for EOL releases over time, and that many industry audits forbid unmaintained runtimes.
  • LTS is not forever. The releases page says LTS status "typically guarantees that critical bugs will be fixed for a total of 30 months."
  • Paid support exists, and the project calls it temporary. The end-of-life page names HeroDevs, NodeSource and TuxCare as providers of commercial services for security fixes through the OpenJS Foundation Ecosystem Sustainability Program, and it says that using EOL releases through commercial support should be viewed as a temporary solution.

Check the releases page before relying on the table, because statuses change as each line moves.

Have another question?