End of life

Node.js 20 end of life

Node.js 20 reached end of life on 30 April 2026. The last release on the line was v20.20.2, published on 24 March 2026. The Node.js project no longer ships security fixes for 20.x, so any vulnerability disclosed since then stays open unless you upgrade to a supported LTS line or use extended security support.

End of life
30 April 2026
Released
Apr 2023
Final release
20.20.2
Successor
Node.js 22 or 24 LTS

Date published by Node.js release schedule. We do not publish a lifecycle date we cannot source.

What actually stops on 30 April 2026

  • Security releases on the 20.x line. v20.20.2 was the last.
  • Updates to the bundled OpenSSL, V8, libuv and npm for the 20.x line.
  • Official Docker image and distribution package updates for Node.js 20.

What actually breaks in the upgrade

Native modules decide the date

Most JavaScript runs unchanged on Node.js 22. Native add-ons compiled against Node 20's ABI must be rebuilt, and some older add-ons no longer build at all. Inventory them before you schedule the upgrade.

Node.js 22 is not the long runway

Node.js 22 reaches end of life on 30 April 2027. Teams upgrading now should consider going straight to the newest LTS line so they do not repeat the exercise in a year.

Your options, costed honestly

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

OptionWhat it isEffortCostOur view
Upgrade to Node.js 22 or 24Rebuild native modules and retest.Days to weeksEngineering timeThe destination. Go to the newest LTS you can.
Extended security supportBackported fixes for Node.js 20 runtimes.DaysSubscriptionFor applications pinned by native modules, vendor certification or a release freeze.
Stay unpatchedNo fixes since March 2026.NoneZero nowNode.js services are usually internet-facing. A poor place to carry risk.

What OSSeva does for Node.js 20

OSSeva patches this line

OSSeva backports security fixes to Node.js 16, 18 and 20 runtimes and helps plan the move to a current LTS line.

Node.js extended support

What your auditor will say

PCI DSS 4.0

Requirement 6.3.3. Payment pages and APIs on an unsupported runtime need patched components or a documented compensating control.

SOC 2

CC7.1. Auditors look for evidence that production runtimes receive security fixes.

Compliance library

Node.js 20: common questions

When did Node.js 20 reach end of life?

On 30 April 2026. The last release was v20.20.2 on 24 March 2026.

Which Node.js versions are still supported?

Node.js 22 is supported until 30 April 2027, and newer LTS lines run longer. Check the Node.js release schedule for current dates.

Can I get security patches for Node.js 20?

Not from the Node.js project. Third-party extended security support, including OSSeva's, backports fixes to the 20.x runtime.

Still running Node.js 20?

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.