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 coveredWhat now
Which vendors provide Node.js 24 security patches after 30 April 2028?
Node.js Extended Support: Patched 14 to 20 Runtimes- 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
| Version | Released | End of life | Status |
|---|---|---|---|
| Node.js 24 (this page) | 6 May 2025 | 30 April 2028 | Approaching |
| Node.js 22 | 24 Apr 2024 | 30 April 2027 | Approaching |
| Node.js 20 | 18 Apr 2023 | 30 April 2026 | End of life |
| Node.js 18 | 19 Apr 2022 | 30 April 2025 | End of life |
| Node.js 16 | 20 Apr 2021 | 11 September 2023 | End of life |
| Node.js 14 | 21 Apr 2020 | 30 April 2023 | End 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.
| Option | What it is | Effort | Cost | Our view |
|---|---|---|---|---|
| Stay on 24 and take each release | Security releases continue to 30 April 2028. | A routine update for each release | Engineering time | The right answer today. |
| Upgrade to Node.js 26 LTS | Rebuild native modules, update base images, retest. | Scales with native modules, base images and test coverage | 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. | Starts from your current version | Subscription, priced per application runtime | Useful 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 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.
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.
Prefer to talk or read more first?