Approaching525 days from today

Node.js 24 end of life

Node.js 24 reaches end of life on 30 April 2028, according to the Node.js release schedule. It was released on 6 May 2025 and moved to maintenance on 20 October 2026, so it gets critical fixes and security updates only. The latest release is 24.22.3, the 11 November 2026 security release. Node.js 26 is supported to April 2029.

What happens to Node.js 24 at its end date?

Assessed case by case. While the Node.js project supports 24, fixes come from its own releases, so OSSeva has no patched build to ship for it yet.

Check if my version is covered

Still on Node 18 or 20? Get extended support

Node.js extended support or ask for a quote

What now

Which vendors provide Node.js 24 security patches after 30 April 2028?

Node.js Extended Support: Patched 14 to 20 Runtimes

Only your email is required · An engineer replies within 1 business day · No commitment

End of life
30 April 2028
Released
May 2025
Final release
24.22.3 (latest, 11 November 2026 security release)
Successor
Node.js 26 LTS (to 30 April 2029)

Date published by Node.js release schedule. We do not publish a lifecycle date we cannot source. Dates checked on endoflife.date and the Node.js release schedule on 17 November 2026.

Last reviewed

Node.js versions: release and end-of-life dates

Node.js release and end-of-life dates
VersionReleasedEnd of lifeStatus
Node.js 24 (this page)6 May 202530 April 2028Approaching
Node.js 2224 Apr 202430 April 2027Approaching
Node.js 2018 Apr 202330 April 2026End of life
Node.js 1819 Apr 202230 April 2025End of life
Node.js 1620 Apr 202111 September 2023End of life
Node.js 1421 Apr 202030 April 2023End of life

End-of-life dates are published by each project and checked against endoflife.date.

What actually stops on 30 April 2028

  • Active LTS ended on 20 October 2026. Since then 24 gets critical bug fixes and security updates only, and new features arrive only where they help migration to later lines.
  • All releases on the 24.x line after 30 April 2028, including security releases.
  • Fixes for the bundled dependencies, such as V8, OpenSSL and undici, which ship inside the node binary and cannot be updated separately.

What actually breaks in the upgrade

24 now, 26 next

Node.js 26 has been LTS since 28 October 2026 and is supported to 30 April 2029, a year longer than 24. A service already on 24 can stay there through 2027 and plan the move to 26 at leisure.

The schedule changes after 26

The release schedule lists Node.js 27 with an alpha from 28 October 2026, a release on 22 April 2027 and end of life on 30 April 2030. Check the schedule before choosing a target in 2027.

Native modules and base images move too

Every native addon has to be rebuilt for a new major, and base images tagged node:24 need to change. Inventory both before setting a date.

Your options, costed honestly

Including the ones that do not involve buying anything from us.

OptionWhat it isEffortCostOur view
Stay on 24 and take each releaseSecurity releases continue to 30 April 2028.A routine update for each releaseEngineering timeThe right answer today.
Upgrade to Node.js 26 LTSRebuild native modules, update base images, retest.Scales with native modules, base images and test coverageEngineering timeA year more runway, to 30 April 2029.
OSSeva support for Node.jsUpgrade path planning and operations, under the same contract as older runtimes.Starts from your current versionSubscription, priced per application runtimeUseful where 24 runs alongside 14 to 20 services that need patched builds.

What OSSeva does for Node.js 24

Assessed case by case

While the Node.js project supports 24, fixes come from its own releases, so OSSeva has no patched build to ship for it yet. OSSeva's Assure tier includes Node.js version upgrade planning and Operate runs major version migrations, so 24 is covered as an upgrade target. Patched builds today are for 14, 16, 18 and 20, and for 22 after 30 April 2027.

Node.js extended support

What your auditor will say

PCI DSS v4 Requirement 6.3.3

Every system component in the cardholder data environment needs its applicable security patches. A component with no upstream fix supply needs a patched source or a documented compensating control.

SOC 2 CC7.1

Auditors ask for evidence that production systems receive security fixes. A version past end of life fails that test unless another supplier ships the fixes and can show which CVEs they close.

Compliance library Node.js end of life dates for every version

Questions

Node.js 24: common questions

Book a 15-minute call

What is the Node.js 24 end of life date?

30 April 2028, according to the Node.js release schedule and endoflife.date (checked 17 November 2026). Node.js 24, codename Krypton, entered LTS on 28 October 2025.

Is Node.js 24 still supported?

Yes. It moved from Active LTS to Maintenance LTS on 20 October 2026 and receives critical bug fixes and security updates until 30 April 2028.

What is the latest Node.js 24 release?

24.22.3, the security release of 11 November 2026.

Should I upgrade from Node.js 24 to 26?

Not urgently. Node.js 26 has been LTS since 28 October 2026 and is supported to 30 April 2029, a year longer than 24, so a service on 24 can plan the move for 2027.

Is Node 24 or Node 26 the better LTS to start on?

For a new service in late 2026, 26 has the longer runway. Node.js 24 is the safer choice if your dependencies and native add-ons are only tested on 24, since both are supported by the Node.js project.

Get a quote

Still running Node.js 24?

Tell us the versions and the estate size. We will tell you honestly whether to upgrade or to buy cover — and we say 'upgrade' more often than you would expect.

Only your email is required · An engineer replies within 1 business day · No commitment

Prefer to talk or read more first?

Book a call