// Node.js extended support

Node.js 18 extended support, and Node.js 20 after end of life.

Patched Node.js 14 to 20 runtimes while you move to a current LTS line.

Node.js extended support from OSSeva means patched Node.js 14, 16, 18 and 20 runtimes after end of life, with V8 and libuv fixes, and Node.js 22 after it ends on 30 April 2027. Critical CVEs (CVSS 9.0 or higher) are fixed within 48 hours and High within 7 days. Priced per application runtime. A senior engineer replies within 1 business day with a quote. Node.js 18 reached end of life on 30 April 2025 with 18.20.8, and Node.js 20 on 30 April 2026, with 20.20.2 as its last release. For most applications the better move is an upgrade to Node.js 24, or to Node.js 26, the LTS line since 28 October 2026, and we will tell you so. Extended support is for runtimes held back by native modules, vendor certification or a release freeze.

Dates checked 17 November 2026 against nodejs.org, endoflife.date and the Node.js release schedule on GitHub.

Node.js 20Node.js 18Node.js 16Node.js 14Node.js 22
Read the 18 and 20 upgrade guide

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

Why Node.js 18 and 20 are still in production

Most Node.js upgrades are a test run and a rebuild. These are the reasons some services do not move.

End of life means known flaws stay open

The Node.js project states that an end-of-life line gets no new releases, even when a vulnerability fixed in a newer line also affects it. Node.js 20 has already missed two security releases, on 17 June and 28 July 2026, which shipped fixes for 22, 24 and 26 only.

Native modules decide the date

Native add-ons are compiled for one Node.js ABI: version 115 on Node.js 20, 127 on 22 and 137 on 24. Each one has to be rebuilt for the new line, and an add-on that no longer builds is what usually pins a service to 18 or 20.

Node.js 22 is a short stop

Node.js 22 reaches end of life on 30 April 2027. Node.js 24 is supported until 30 April 2028, and 26 until 30 April 2029. A team that moves to 22 now faces the same exercise again within months.

The dates that matter

  1. 2025-03-27

    Node.js 18.20.8 released, the final 18.x release.

  2. 2025-04-30

    Node.js 18 reaches end of life.

  3. 2026-03-24

    Node.js 20.20.2 released, the final 20.x release.

  4. 2026-04-30

    Node.js 20 reaches end of life.

  5. 2026-06-17

    Security releases ship for Node.js 22, 24 and 26. None for 20.

  6. 2026-07-28

    A second round of security releases for 22, 24 and 26. None for 20.

  7. 2026-10-28

    Node.js 26 becomes an LTS line, supported until 30 April 2029.

  8. 2027-04-30

    Node.js 22 reaches end of life.

  9. 2028-04-30

    Node.js 24 reaches end of life.

What OSSeva delivers

1

Patched Node.js 14 to 22 runtimes

Security fixes backported to the Node.js line you run (22 from its 30 April 2027 end of life), with V8 and libuv CVEs included, delivered as signed Docker images in Alpine and Debian variants, apt and yum packages and binaries. You change the image tag and nothing else.

OSSeva PatchV8 and libuvSigned (GPG)
2

Dependency scanning and an upgrade plan

Transitive npm dependency scanning with a prioritised remediation report, an HTTP/2 and TLS configuration review, a container base image hardening review, a SOC 2 and PCI DSS attestation package and a plan for the move to a current LTS line.

OSSeva Assurenpm scanningUpgrade plan
3

Node.js operated

24/7 process and cluster health monitoring, event loop and memory leak alerting, PM2 and cluster mode support, a 15-minute P1 incident response SLA, a named senior Node.js engineer, and execution of the major version migration.

OSSeva Operate24/715-minute P1

Audit questions

Audit questions on end-of-life software are answered in the PCI DSS 6.3.3 and FedRAMP and CMMC guides.

What does it cost to patch unsupported Node.js?

OSSeva prices Node.js extended support per application runtime, and does not publish a price list. Three things set the figure: how many application runtimes you run, which Node.js lines they are on, and which tier you choose (Patch, Assure or Operate). The other cost is your own engineering time, for testing patched builds and for the upgrade you still plan to do.

To set that against the cost of moving, enter your own numbers in the upgrade vs extended support calculator. The cost guide lists what to count on each side.

How fast are CVE patches for EOL Node.js?

Critical CVEs (CVSS 9.0 or higher) are fixed within 48 hours and High CVEs within 7 days on the Patch tier. Everything else goes into a quarterly batch, and Assure adds 24/7 reactive support.

Node.js ships security releases for 22, 24 and 26 only, so each one adds CVEs that stay open on an ended 20.x or 18.x line. The CVE tally lists every release and the fixes each one carried.

Should you upgrade Node.js instead of buying patches?

Upgrade whenever the application can be retested on a newer line before your next audit or release freeze. Buy patches when a native add-on that will not build, a vendor certification or a freeze holds a service on 18 or 20, and treat them as a bridge to the upgrade.

The upgrade guide lists the changes that break real applications between 18 or 20 and 22 or 24, in the order to fix them.

How is this different from HeroDevs NES or TuxCare ELS?

All three ship patched Node.js 18 and 20 runtimes. HeroDevs and TuxCare also cover 12, 14 and 16 and sell Node.js alongside other runtimes and frameworks, while OSSeva covers Node.js under the same contract as the brokers, databases and Java stack around it, and its Operate tier runs them with a 15-minute P1 response. HeroDevs is the better fit when your exposure is mostly JavaScript and front-end frameworks.

From each vendor's own pages, read 17 November 2026. Confirm terms with the vendor before you buy.

ProviderNode.js versions listedPatch timing as published
OSSeva14, 16, 18, 20; 22 after 30 April 2027Critical within 48 hours, High within 7 days
HeroDevs NES12, 14, 16, 18 and 20Fix targets of 14 days for Critical and 30 days for High (published SLA)
TuxCare ELS12, 14, 16, 18 and 20; 22 when it endsSLA-backed; no timings on the Node.js page

Which Node.js versions are covered?

OSSeva ships patched runtimes for Node.js 14, 16, 18 and 20 today, and for 22 after its end of life on 30 April 2027. Node.js 24 and 26 are still supported by the Node.js project, so they get upgrade planning on Assure and migrations on Operate rather than patched builds.

Node.js lineEnd of lifeOSSeva coverage
1430 April 2023Patched runtime
1611 September 2023Patched runtime
1830 April 2025Patched runtime
2030 April 2026Patched runtime
2230 April 2027Patched runtime after that date
2430 April 2028Upgrade planning (Assure) and migration (Operate)
2630 April 2029Upgrade planning (Assure) and migration (Operate)

End dates from the Node.js release schedule and endoflife.date, checked 17 November 2026.

Which vendors provide Node.js 20 security patches after 30 April 2026?

OptionWhat you getTrade-off
Upgrade to Node.js 24An LTS line the project supports until 30 April 2028Native add-ons are rebuilt and deprecated APIs cleared. For most applications this is the right answer.
Upgrade to Node.js 26The longest runway: an LTS line since 28 October 2026, supported until 30 April 2029The biggest jump from 18 or 20, so more native add-ons and deprecated APIs to clear.
Upgrade to Node.js 22The smallest step from 20End of life on 30 April 2027, so another upgrade follows soon.
Commercial support for end-of-life linesFixes for lines past Maintenance LTS, through the partners the Node.js project lists and other support companiesCheck what each one covers: the runtime only, or images, npm dependencies and operations too.
OSSeva extended supportPatched 14 to 20 runtimes, npm dependency scanning and help with the upgrade, on one contract with the rest of your stackA subscription priced per application runtime, for as long as you stay.
Stay unpatchedNothingNode.js services are usually internet-facing, and every new security release adds findings you cannot close.

Dates from the Node.js release schedule on GitHub and the nodejs.org release index, release policy and end-of-life pages, checked on 9 October 2026; the Node.js 26 LTS date re-read on nodejs.org and the release schedule on 15 November 2026. OSSeva coverage from the OSSeva Node.js technology page.

Questions

Frequently asked questions

Book a 15-minute call

How quickly are Node.js CVEs patched after end of life?

Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days, as published for the Patch tier. Everything else goes into a quarterly batch. This applies to the patched Node.js 14, 16, 18 and 20 runtimes, and Assure adds 24/7 reactive support.

What does Node.js extended support cost?

It is priced per application runtime, as the pricing page explains. The tier you choose, Patch, Assure or Operate, sets how much of the work OSSeva takes on. A senior engineer replies within 1 business day with a quote.

When did Node.js 18 reach end of life?

On 30 April 2025. The final release was 18.20.8, published on 27 March 2025, and the Node.js project publishes no further 18.x releases.

When is Node.js 20 end of life?

Node.js 20 reached end of life on 30 April 2026. Its last release was 20.20.2 on 24 March 2026, and the security releases of June and July 2026 shipped no 20.x build.

Is there extended support for Node.js 18?

Yes, from commercial providers. The Node.js project points to its OpenJS Ecosystem Sustainability Program partners for lines past Maintenance LTS, and independent support companies such as OSSeva also patch them. OSSeva covers Node.js 14, 16, 18 and 20, including V8 and libuv fixes.

Which Node.js versions are supported now?

Node.js 22 until 30 April 2027 and Node.js 24 until 30 April 2028. Node.js 26 has been LTS since 28 October 2026 and is supported until 30 April 2029.

Should we upgrade instead of buying extended support?

Usually, yes. For most applications moving to 24 means a test run and a rebuild of native add-ons. Extended support is for runtimes that cannot move yet because of a native dependency, a vendor certification or a release freeze. The Node.js 18 and 20 to 22 and 24 upgrade guide covers the move.

Does OSSeva support current Node.js versions?

Yes. Node.js 22 is covered alongside the patched 14 to 20 lines, and OSSeva Assure plans the move to a current LTS line.

Do the patched images work with our Kubernetes manifests?

Yes. OSSeva publishes patched Node.js Docker images in Alpine and Debian variants. You update the image tag in your manifests and nothing else changes.

Get a quote

Upgrade what you can.
Patch what you cannot.

Book a discovery call with your Node.js versions and native dependencies, and we will send a quote priced per application runtime.

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

Prefer to talk or read more first?

Book a call