Approaching162 days from today

Node.js 22 end of life

Node.js 22 reaches end of life on 30 April 2027, according to the Node.js release schedule. It was released on 24 April 2024 and has been in maintenance since 21 October 2025, so it gets security and critical fixes only. The latest release is 22.23.5, the 11 November 2026 security release. Node.js 24 is supported to April 2028.

Who patches Node.js 22 after its end date?

OSSeva patches Node.js 22 after its end date under its patch SLA: Critical fixes within 48 hours and High within 7 days.

Check if my version is covered

What now

Which vendors provide Node.js 22 security patches after 30 April 2027?

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 2027
Released
Apr 2024
Final release
22.23.5 (latest, 11 November 2026 security release)
Successor
Node.js 24 LTS (to 30 April 2028) or 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 246 May 202530 April 2028Approaching
Node.js 22 (this page)24 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 2027

  • Maintenance releases on the 22.x line after 30 April 2027.
  • Security fixes. Node.js security releases cover the supported lines only. CVE-2026-56848, an HTTP/2 heap use-after-free fixed in the July 2026 releases, lists Node.js 22, 24 and 26 as affected, and lines past end of life are not assessed.
  • Fixes for the bundled dependencies, such as V8, OpenSSL, undici and llhttp, which ship inside the node binary and cannot be updated separately.

What actually breaks in the upgrade

24 or 26

Node.js 24 is in maintenance from 20 October 2026 and reaches end of life on 30 April 2028. Node.js 26 has been LTS since 28 October 2026 and is supported to 30 April 2029. For a move planned in 2027, 26 gives a year more for the same work.

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. From 27, Node.js ships one major release a year instead of an odd and even pair.

Native modules and Docker bases move too

Every native addon has to be rebuilt against the new ABI, and base images tagged node:22 need to change. Inventory both before you set a date.

Your options, costed honestly

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

OptionWhat it isEffortCostOur view
Upgrade to Node.js 26 LTSRebuild native modules, update base images, retest.Scales with native modules, base images and test coverageEngineering timeThe longest supported target, to 30 April 2029.
Upgrade to Node.js 24 LTSA shorter hop, already in wide use.Scales with native modules, base images and test coverageEngineering timeFine, but it ends a year before 26.
OSSeva patched Node.js 22Signed node binaries and images with backported security fixes after 30 April 2027: Critical CVEs within 48 hours, High within 7 days.Starts from your current versionSubscription, priced per application runtimeFor services that cannot be rebuilt and retested by April 2027.
Stay on 22 after the dateNo upstream fixes after 30 April 2027.NoneZero nowNode runs at the edge of most stacks. Hard to defend once advisories stop covering it.

What OSSeva does for Node.js 22

OSSeva patches this line

OSSeva ships patched, signed Node.js 22 binaries and container images after 30 April 2027, with backported fixes for Node.js core and its bundled dependencies. Coverage is on the Patch, Assure and Operate tiers, as it is today for Node.js 14, 16, 18 and 20.

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 22: common questions

Book a 15-minute call

When does Node.js 22 reach end of life?

On 30 April 2027, according to the Node.js release schedule and endoflife.date (checked 17 November 2026). Node.js 22 entered LTS on 29 October 2024 and moved to Maintenance LTS on 21 October 2025.

Is Node.js 22 still supported?

Yes, in Maintenance LTS. Since 21 October 2025 it receives security and critical fixes only, until 30 April 2027. The latest release is 22.23.5, the security release of 11 November 2026.

What happens to Node.js 22 on 30 April 2027?

The Node.js project stops releasing fixes for the 22.x line, including security releases. Later Node.js security announcements cover only supported lines and treat ended ones as affected, and the bundled V8, OpenSSL and undici stay at the versions in the last release.

Should I upgrade from Node.js 22 to 24 or 26?

26 if the move happens in 2027. Node.js 26 has been LTS since 28 October 2026 and is supported to 30 April 2029, a year longer than 24, which ends on 30 April 2028.

How is Node.js 22 end of life different from Node.js 20?

Node.js 22 still gets security releases today. Node.js 20 ended on 30 April 2026 and has already missed four security releases, so 22 is the line to plan a move for now.

Can I get security patches for Node.js 22 after April 2027?

Yes. OSSeva ships patched, signed Node.js 22 builds on the Patch, Assure and Operate tiers, with Critical CVEs fixed within 48 hours and High within 7 days.

Get a quote

Still running Node.js 22?

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