Tech

Explainer

Updated

Is Node.js 18 still supported?

Key facts

The Node.js releases page lists v22, v24 and v26 as LTS lines, while v18 carries the status EOL.

No, Node.js 18 has reached end-of-life, so the Node.js project no longer maintains it. The Node.js releases page lists v18 (Hydrogen) 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."

Node.js release lines from v18 to v26

The releases page gives each line a status and a Last updated date. It gives no end-of-life date for any line.

Node.js lineStatusLast updated
v26 (Lithium)LTSNov 10, 2026
v25EOLMar 31, 2026
v24 (Krypton)LTSNov 10, 2026
v23EOLMay 14, 2025
v22 (Jod)LTSNov 11, 2026
v21EOLApr 10, 2024
v20 (Iron)EOLMar 24, 2026
v19EOLApr 10, 2023
v18 (Hydrogen)EOLMar 27, 2025

Node.js 22 is shown as LTS on the same page. Its status has its own page: Is Node.js 22 still supported?

What changed and when

The releases page also gives each line's first release date. For v18 it is Apr 18, 2022, and v26 was first released May 05, 2026.

For v18, the Last updated date is Mar 27, 2025. The page labels that column Last updated and does not call the date an end-of-life date, so this page does not state one for v18.

The releases page also describes how the release pattern changed. Up to Node.js 26, odd-numbered releases became unsupported after six months, and even-numbered releases moved to Active LTS. Starting with Node.js 27, the release cycle becomes annual, and every major version moves to LTS status after six months in Current and six more months in Alpha.

Edge cases a reader meets next

  • An EOL line gets no patches from the project. The end-of-life page says that when newer lines get security releases, EOL lines get no new release, even when the same vulnerability affects them. The same page lists 15 high, 19 medium and 4 low vulnerability counts for v18 in its Vulnerabilities column.
  • LTS is not forever. The releases page says LTS status "typically guarantees that critical bugs will be fixed for a total of 30 months."
  • Production use has a rule. The releases page says production applications should use only Active LTS or Maintenance LTS releases. For v18 that means moving to a line the table marks LTS.
  • Paid support exists, and the project calls it temporary. The releases page says commercial support past the Maintenance LTS phase comes through OpenJS Ecosystem Sustainability Program partners. The end-of-life page names HeroDevs, NodeSource and TuxCare as providers of security fixes for EOL versions, and it says that using EOL releases this way 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?