---
title: "Node.js Version EOL: Supported Versions and End-of-Life Guide"
description: "Check Node.js version EOL dates, LTS releases, supported versions, and upgrade guidance. Learn why keeping Node.js updated matters for security and production."
url: "https://www.gowrishankar.me/blog/nodejs-version-eol"
author: "Gowri Shankar Balasubramaniam"
published: 2026-10-01T21:34:37.486Z
category: "Node.js"
tags: ["Node.js 22 EOL","Node.js 24 LTS","Node.js EOL","Node.js EOL 2026","Node.js LTS","Node.js end of life","Node.js security","Node.js upgrade","Node.js version support"]
---

# Node.js Version EOL: Supported Versions and End-of-Life Guide

> Check Node.js version EOL dates, LTS releases, supported versions, and upgrade guidance. Learn why keeping Node.js updated matters for security and production.

**Node.js 24 is currently an LTS release**, while Node.js 26 is the Current release. Node.js 22 also remains supported as an LTS release.

## Node.js EOL Status

| Version | Status | EOL |
| --- | --- | --- |
| Node.js 26 | Current | - |
| Node.js 24 | LTS | April 2028 |
| Node.js 22 | LTS | April 2027 |
| Node.js 20 | EOL | March 2026 |
| Node.js 18 | EOL | March 2025 |

Node.js recommends using **Active LTS or Maintenance LTS releases for production applications**. Once a Node.js version reaches EOL, it no longer receives official security updates and vulnerability fixes.

For production environments, organizations should maintain a regular Node.js upgrade lifecycle and migrate applications before their runtime reaches EOL. This helps reduce security risks, dependency compatibility issues, and potential compliance concerns.

**Recommended approach:** Check your installed version with `node --version` and plan upgrades before the published EOL date.

---

Source: https://www.gowrishankar.me/blog/nodejs-version-eol