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, became LTS on 28 October 2025 and moves to maintenance on 20 October 2026, after which it receives critical bug fixes and security updates only. The latest release is 24.21.0, from 7 September 2026. Node.js 26 is supported to April 2029.
- End of life
- 30 April 2028
- Released
- May 2025
- Final release
- 24.21.0 (latest, 7 September 2026)
- 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.
Last reviewed
What actually stops on 30 April 2028
- Active LTS on 20 October 2026. From 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 becomes LTS on 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.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Stay on 24 and take each release | Security releases continue to 30 April 2028. | Hours per release | Engineering time | The right answer today. |
| Upgrade to Node.js 26 LTS | Rebuild native modules, update base images, retest. | Weeks | Engineering time | A year more runway, to 30 April 2029. |
| OSSeva support for Node.js | Upgrade path planning and operations, under the same contract as older runtimes. | Days | Subscription | Useful where 24 runs alongside 14 to 20 services that need patched builds. |
What OSSeva does for Node.js 24
Assessed case by case
Node.js 24 is not yet in OSSeva's Node.js versions table, which lists 14 to 22. While the project supports 24, fixes come from its own releases. 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.
Node.js extended supportWhat your auditor will say
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.
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.
Node.js 24: common questions
What is the Node.js 24 end of life date?
30 April 2028, according to the schedule in the nodejs/Release repository.
Is Node.js 24 still supported?
Yes. It is in Active LTS until 20 October 2026, then in maintenance, with critical bug fixes and security updates, until 30 April 2028.
What is the latest Node.js 24 release?
24.21.0, released on 7 September 2026.
Should I upgrade from Node.js 24 to 26?
Eventually. Node.js 26 becomes LTS on 28 October 2026 and is supported to 30 April 2029, a year longer than 24.
What is the Node.js 24 codename?
Krypton.
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.