OSSeva Blog
SecurityWho Provides Node.js Security Patches After End of Life? (Node 18 and 20)
The short answer
Four providers publish security patches for Node.js 18 and 20 after the Node.js project stopped: HeroDevs (Never-Ending Support, Node.js 12 to 20), TuxCare (Endless Lifecycle Support, Node.js 12 to 20), OSSeva (patched Node.js 14 to 20 runtimes, with V8 and libuv fixes included; see Node.js extended support for 18 and 20) and Canonical (Ubuntu Pro, for the nodejs package that Ubuntu itself ships). The Node.js project's own end-of-life page points to HeroDevs and TuxCare through the OpenJS Foundation's Ecosystem Sustainability Program.
For the OSSeva offer itself, Node.js 18 extended support, and Node.js 20 after end of life sets out the versions covered, and Node.js end-of-life dates has the dates. Front-end code on those servers has its own end-of-life dates: see Next.js end of life and React end of life.
The project ended Node.js 18 on 30 April 2025 and Node.js 20 on 30 April 2026. Upgrading to a Node.js version that still has long-term support (LTS), such as 22, 24 or 26, remains the long-term answer; paid support is how you stay patched while that happens.
OSSeva publishes this list and is one of the four providers in it. The HeroDevs and TuxCare facts were re-read on those vendors' own pages on 17 November 2026, and the Canonical and NodeSource facts were checked on 28 October 2026. OSSeva's row comes from our own Node.js page.
Running Node.js in production? OSSeva patches and supports it, end-of-life versions included.
Node.js extended support: what is coveredBest for: which provider fits which situation
| Provider | Best for | Versions covered | Support model |
|---|---|---|---|
| HeroDevs Never-Ending Support | Node.js that sits beside other end-of-life JavaScript frameworks, or runs as containers and serverless functions | Node.js 12, 14, 16, 18 and 20 | Drop-in container images and binaries; SLA-backed patch delivery tied to severity (SLA available on request); AWS, Azure, Google Cloud and on premises |
| TuxCare Endless Lifecycle Support | Teams that want fixes through npm and their existing toolchain, or that already buy TuxCare for other runtimes | Node.js 12, 14, 16, 18 and 20; 22 to be added when it reaches end of life | Signed patches from TuxCare-hosted repositories, with SBOM and VEX documents and 24/7 expert assistance |
| OSSeva | Self-managed Node.js 14 to 20 that needs patched runtimes, with the option of 24/7 operations or upgrade planning | Node.js 14, 16, 18 and 20 now; 22 after its end of life on 30 April 2027 | Subscription in three tiers (Patch, Assure, Operate); GPG-signed Docker images, apt and yum packages and binaries; Operate adds 24/7 monitoring and a 15-minute P1 response |
| Canonical (Ubuntu Pro) | Node.js installed from Ubuntu's own nodejs package | The version each Ubuntu release ships (18.19.1 on 24.04 LTS) | Ubuntu Pro subscription; fixes arrive through apt via ESM Apps |
How we chose these providers
The question here is narrow: who ships security fixes for a Node.js line after the Node.js project has stopped? We started from the three providers the Node.js project's own end-of-life page names, then added anyone else whose public pages show a patch path for Node.js 18 or 20. A provider stays on the list if it passes all of these tests, and OSSeva was held to the same ones.
- It delivers fixes, not only advice. A patched Node.js runtime or package for a line past its end-of-life date. An assessment, a roadmap or an upgrade service does not meet this test.
- The coverage is public. Either the provider names the Node.js lines on its own page (HeroDevs, TuxCare and OSSeva do), or the covered package is one you can look up (Canonical: Ubuntu 24.04 ships
nodejs18.19.1 in universe, and Canonical's ESM page says ESM Apps covers all universe packages). - It installs without changing application code. A drop-in image, binary or package you can pull through your own registries or package manager.
- The offer is current. HeroDevs and TuxCare were checked on 17 November 2026, Canonical and NodeSource on 28 October 2026.
Two things are left out on purpose. The Node.js project, because it stopped patching 18 and 20. NodeSource, which the Node.js end-of-life page also lists: its upgrade page describes assessments, a migration roadmap and optional temporary security support, but does not say it ships patched runtimes, so it fails the first test. We compared what providers publish. We did not run their builds or audit their claims. A provider missing from this list is one we did not verify, not one we judged unfit, and the order of the rows is not a ranking.
Node.js end-of-life dates
| Line | Codename | End of life | Status on 17 November 2026 | Security releases missed |
|---|---|---|---|---|
| Node.js 16 | Gallium | 11 September 2023 | No upstream fixes | All since 11 September 2023 |
| Node.js 18 | Hydrogen | 30 April 2025 | No upstream fixes; last release 18.20.8 | 8 since 30 April 2025 |
| Node.js 20 | Iron | 30 April 2026 | No upstream fixes; last release 20.20.2 | 4 since 30 April 2026 |
| Node.js 22 | Jod | 30 April 2027 | Maintenance LTS since 21 October 2025: security and critical fixes | None |
| Node.js 24 | Krypton | 30 April 2028 | Maintenance LTS since 20 October 2026 | None |
| Node.js 26 | Lithium | 30 April 2029 | LTS since 28 October 2026 | None |
Dates are from the Node.js release schedule and endoflife.date, and the missed-release counts from the Node.js security announcements as tallied in our CVE guide. Once a line ends, new advisories in Node.js security releases name only the supported lines, so a scanner may stay quiet about Node.js 18 or 20 while the vulnerable code is still there. Our Node.js vulnerabilities by version lists the CVEs published since each line ended.
How do I know when my Node.js version reaches end of life?
Run node --version to find your major line, then look it up on the Node.js release schedule at nodejs.org. Each line moves from Current to Active LTS, then Maintenance LTS, then end of life, on fixed dates. On 17 November 2026 Node.js 18 and 20 are already past end of life, Node.js 22 ends on 30 April 2027 and Node.js 24 on 30 April 2028.
The release schedule, checked on 17 November 2026, puts the Node.js versions in these phases. Active LTS (long-term support with new fixes and backports): Node.js 26, which entered it on 28 October 2026. Maintenance LTS (security and critical fixes only): Node.js 22 and 24. End-of-life Node.js versions: 20, 18, 16 and every earlier line. Odd-numbered lines such as Node.js 25 never enter LTS and end within months of release; Node.js 25 ended on 1 June 2026, so a production service should not run on one.
When your line reaches end of life, the Node.js project stops releasing fixes for it. Add the end date to your inventory when you pick a version, so the upgrade or support decision is made before the date, not after.
Node.js end-of-life support providers compared
Each row reflects what the vendor publishes on its own site: HeroDevs and TuxCare as of 17 November 2026, Canonical as of 28 October 2026.
| Provider | What it covers | Versions | Delivery model | Self-managed? |
|---|---|---|---|---|
| HeroDevs Never-Ending Support | Security fixes for all severity levels backported to end-of-life Node.js, SLA-backed by severity, with compliance support for frameworks such as SOC 2, PCI DSS, HIPAA and FedRAMP | 12, 14, 16, 18 and 20 | Container images and binaries, as a drop-in replacement; AWS, Azure, Google Cloud and on premises | Yes |
| TuxCare Endless Lifecycle Support | Backported, tested and signed security patches, SLA-backed, with SBOM and VEX documentation and 24/7 expert assistance | 12, 14, 16, 18 and 20; TuxCare says 22 will be added when it reaches end of life | Through npm and your existing package managers and build tools | Yes |
| OSSeva | Quarterly CVE patches for the Node.js runtime, with V8 engine and libuv fixes included; upgrade planning and 24/7 operations on higher tiers | 14, 16, 18 and 20; 22 after its end of life on 30 April 2027 | GPG-signed Docker images (Alpine and Debian), apt and yum packages, and binaries | Yes |
| Canonical (Ubuntu Pro) | Security maintenance for the nodejs package in Ubuntu's universe component through ESM Apps | The version each Ubuntu release ships (18.19.1 on Ubuntu 24.04 LTS) | APT packages on Ubuntu | Yes, on Ubuntu |
Canonical's coverage follows the Ubuntu package, not the upstream line. If your services run the official Node.js tarballs or Docker images rather than Ubuntu's package, Ubuntu Pro does not patch them. NodeSource, which the Node.js site also lists, sells an upgrade programme: assessments, a migration roadmap and support tickets, plus optional temporary security support. Its page does not say it ships patched runtimes, so it is not in the table.
How quickly are CVE patches released for end-of-life Node.js?
With OSSeva Patch, a Critical (CVSS 9.0 and above) fix for Node.js 18 or 20 ships within 48 hours and a High within 7 days (see the OSSeva support SLA). The other two providers publish different things, so the table below shows only what each one states on its own page.
| Provider | Stated patch window | Source, checked 17 November 2026 |
|---|---|---|
| OSSeva Patch | Critical (CVSS 9.0+) within 48 hours; High within 7 days | OSSeva support SLA |
| HeroDevs NES | Fix targets of 14 days for Critical and 30 days for High severity (priority P0 and P1); 60 days for Medium and 90 days for Low (P2). Its Node.js page says only "SLA-backed patch delivery tied to severity" | docs.herodevs.com/sla and herodevs.com/support/node-nes |
| TuxCare ELS | Not stated on the Node.js page, which says patches are "SLA-backed" and under a "contractual SLA" | tuxcare.com/endless-lifecycle-support/nodejs-eol-support |
HeroDevs calls its figures targets, made with "extraordinary" or "commercially reasonable" efforts. Ask any provider for the SLA in writing before you sign, and ask what counts as the start of the clock: disclosure, a fixed upstream release or your ticket. Our Node.js vulnerabilities by version shows which advisories each ended line has already missed.
What does patching unsupported Node.js cost?
Cost is set per runtime environment and tier, not per CVE, and the bigger cost is usually the engineering time an upgrade would take. OSSeva prices Node.js per application runtime; see how OSSeva pricing works and the upgrade vs extended support calculator to set it against the cost of moving.
The other two providers, as published on 14 November 2026 (HeroDevs' pricing page was read again on 17 November 2026 and still shows custom pricing):
- HeroDevs: its pricing page shows "Custom Pricing" on the Node.js card, billed annually, with multi-year options. No figure is published.
- TuxCare: its pricing page is a quote request ("pricing based on your environment"). Its online checkout for ELS for Runtimes, which includes Node.js, sells by runtime instance, says ELS is sold annually, and showed a Bronze band of up to 10 instances at $5,000.00 in the order summary. Confirm the current price and what the band covers with TuxCare before you rely on it.
How does HeroDevs Never-Ending Support for Node.js work?
HeroDevs Never-Ending Support (NES) is a subscription for a drop-in replacement of an end-of-life Node.js version. Its page lists Node.js 12, 14, 16, 18 and 20, says it installs with no application code changes, and runs on AWS, Azure, Google Cloud and on premises.
Patches are SLA-backed and tied to severity, and HeroDevs says it is an authorized CVE Numbering Authority that publishes a CVE entry for each fix, listing more than 100 so far for Node.js. It pitches 1 to 3 years of runway to migrate. OSSeva's difference, as set out in our HeroDevs alternative comparison: Node.js sits under the same contract as the brokers and databases around it, and the Operate tier adds 24/7 operations with a 15-minute P1 response. HeroDevs is the better fit when your exposure is mostly front-end and JavaScript frameworks.
Which Node.js versions does TuxCare cover?
TuxCare Endless Lifecycle Support lists Node.js 12, 14, 16, 18 and 20 on its Node.js page (last modified 22 October 2026, read on 17 November 2026), and says Node.js 22 is added when it reaches end of life. The page also lists SBOM and VEX documents for each patched release and shows SLSA Level 3 as coming soon. OSSeva lists 14, 16, 18 and 20, with 22 after 30 April 2027; TuxCare also lists 12. Delivery is through npm and your existing toolchain, from TuxCare-hosted repositories with signed packages, SBOM and VEX documents and 24/7 expert assistance, and TuxCare says fixes for direct and transitive Node.js dependencies are included at no extra cost. See OSSeva vs TuxCare for the layers each one covers.
How the providers differ
HeroDevs
HeroDevs describes its offer as the only end-of-life Node.js support endorsed by the OpenJS Foundation; that is its own claim, and the Node.js end-of-life page lists HeroDevs, NodeSource and TuxCare together. HeroDevs lists Never-Ending Support for 19 JavaScript frameworks and libraries, including AngularJS, Vue 2, Express, Next.js and React, so it fits estates where Node.js sits next to old versions of those. Its Node.js product ships container images and binaries, and it lists coverage across serverless functions, Kubernetes and virtual machines. Our OSSeva vs HeroDevs comparison goes into the overlap.
TuxCare
TuxCare delivers through the package managers you already use and ships SBOM and VEX documents with each release, which suits teams that already buy its operating-system or library coverage. It also covers Python, PHP, Java (OpenJDK), Ruby and .NET runtimes. See OSSeva vs TuxCare.
OSSeva
OSSeva for Node.js ships patched runtimes for Node.js 14, 16, 18 and 20. V8 and libuv vulnerabilities are assessed against each covered line and backported into the Node.js build, so there is no separate engine contract. The images are drop-in replacements for Kubernetes manifests: you change the tag. The Assure tier adds transitive npm dependency scanning, HTTP/2 and TLS configuration review and upgrade path planning; Operate adds 24/7 monitoring, PM2 and cluster-mode support, and runs the major-version migration with you.
Canonical
If your Node.js comes from Ubuntu's own nodejs package, Ubuntu Pro is the simplest option: fixes arrive through apt. On Ubuntu 24.04 LTS that package is Node.js 18. It does nothing for Node.js installed from other sources.
Should you upgrade Node.js or use extended support?
Upgrade when the service is under active development and nothing blocks the move; buy time when native modules, vendor certification or a change freeze block it. Most teams end up doing both, service by service. For the services you cannot move in time, Node.js extended support for 18 and 20 covers them while the upgrade runs. These questions sort each service into one column:
| Question | Points to upgrading now | Points to extended support first |
|---|---|---|
| How many services run the old line? | A handful, with active owners | Dozens, or some with no clear owner |
| Do native addons or pinned packages block the move? | No, npm ci and tests pass on 22 or 24 | Yes, addons need rebuilding or dependencies have no compatible release |
| Is the service changing anyway? | Yes, it is under active development | No, it is stable or due for retirement |
| Is an audit or customer questionnaire coming? | The upgrade can land first | Evidence of a supported runtime is needed before the upgrade can |
| Is the service exposed to the internet? | Either way, exposure makes the open advisories urgent | Patch now if the upgrade will take more than a release cycle |
For Node.js 20, the jump to 22 is small for most code. For Node.js 18 or 16, the breaking changes accumulate, and the slowest dependency usually sets the date. Our Node.js 18 or 20 to 22 or 24 upgrade guide lists the breaking changes, steps and rollback.
If you buy support, treat it as a dated plan rather than a destination. The Node.js project describes commercial support for end-of-life lines as a temporary solution, with upgrading as the goal. Record the upgrade date for each service in your end-of-life inventory, and check that the contract covers the line you will be on until then. Node.js 22 itself ends on 30 April 2027.
Where OSSeva fits
See Node.js extended support for 18 and 20 for the offer and Node.js EOL dates for every version for the calendar. OSSeva patches the Node.js runtime itself, including V8 and libuv, for Node.js 14 to 20, delivered as signed images and packages through your existing registries. Teams with brokers, databases or ZooKeeper on old versions can cover those under the same contract. The extended support vendor roundup compares OSSeva, HeroDevs, TuxCare and others by technology layer.
Shortlisting providers? 12 questions to ask a Node.js extended support vendor turns this comparison into a checklist, and how the NES, ELS and stay-put models differ explains what each model delivers.
Frequently asked questions
Who provides security patches for Node.js 18 and 20 after end of life?
HeroDevs (Never-Ending Support), TuxCare (Endless Lifecycle Support) and OSSeva all publish patched builds for Node.js 18 and 20. Canonical patches the Node.js package that Ubuntu ships, which is Node.js 18 on Ubuntu 24.04 LTS.
Compare Node.js end-of-life support companies: how are they different?
HeroDevs pairs Node.js with support for other end-of-life JavaScript frameworks. TuxCare delivers through your package managers with SBOM and VEX data and covers many other runtimes. OSSeva includes V8 and libuv fixes in its Node.js builds and can also run the service 24/7 alongside brokers and databases. Canonical covers only Ubuntu's own package.
Should we upgrade Node.js or use extended support?
Upgrade services that are under active development and have no blocking dependencies. Use extended support for the rest while they migrate, with a recorded upgrade date for each. Doing neither leaves new runtime advisories open.
How fast are security patches released for end-of-life Node.js?
OSSeva Patch fixes Critical (CVSS 9.0+) issues within 48 hours and High within 7 days. HeroDevs publishes targets of 14 days for Critical and 30 days for High in its SLA documentation. TuxCare's Node.js page says its patches are SLA-backed but states no number. Checked 17 November 2026.
Does Node.js 20 still get security updates?
Not from the Node.js project. Its last release was 20.20.2, and the line ended on 30 April 2026. Fixes for Node.js 20 now come only from commercial providers.
Is Node.js 22 safe to move to?
Yes, but it is already in maintenance and ends on 30 April 2027. Node.js 24, supported to 30 April 2028, gives a longer runway, and Node.js 26, which became LTS on 28 October 2026, runs to 30 April 2029.
Sources
The HeroDevs and TuxCare Node.js pages, the HeroDevs SLA and pricing page and the Node.js end-of-life page were read on 17 November 2026; the TuxCare pricing and checkout pages on 17 November 2026; the Canonical and NodeSource pages on 28 October 2026. The only price quoted is the TuxCare checkout figure above.
- Node.js project: nodejs.org/en/eol and the release schedule, with endoflife.date for last release numbers
- HeroDevs: Node.js Never-Ending Support and its support index, pricing and service level agreement
- TuxCare: Node.js ELS and runtimes ELS, pricing and online checkout for ELS for Runtimes
- Canonical: Ubuntu ESM, and Launchpad publishing records for
nodejsin Ubuntu 24.04 (noble) - NodeSource: Node.js upgrade
- OSSeva: our own Node.js page
Tags
Related articles
How to Choose a Node.js Extended Support Vendor: 12 Questions to Ask
November 17, 2026Security.NET 8 Extended Support After 10 November 2026: Who Patches It Now
October 6, 2026OperationsNES, ELS and Stay-Put Support for Node.js: How the Models Differ
November 17, 2026SecurityOpen Source Security vs Support: Which Fixes Risk Faster?
October 6, 2026OperationsWhat It Costs to Patch Unsupported Node.js: Upgrade vs Extended Support
November 17, 2026OperationsUpgrade Node.js or Buy Third-Party Patches? A Decision Framework
November 17, 2026Get a quote
Ready to get your open source under control?
Tell us what you run. An OSSeva engineer replies within 1 business day with CVE coverage and a price for your stack.
Prefer to talk or read more first?