Node.js 18 End of Life: Which Vendors Offer Extended Security Support?

By Scott Bissett Updated: November 22, 2026 EOL: April 30, 2025 5 min read

Node.js 18 is end of life. It has not received security patches since April 30, 2025. Any CVE disclosed after that date is an unpatched vulnerability in your production environment. Organizations running Node.js 18 need either a migration plan or a commercial extended support contract — now.

Quick answer: Node.js 18 reached end of life (EOL) on April 30, 2025. Active support ended on October 18, 2023. Every Node.js version's release and end-of-support date is on the Node.js lifecycle page. Running a Node.js version that is past end of life? See the support options on this page ↓

Key Dates at a Glance

Node.js 18 lifecycle timeline

Active LTS
Oct 2022 – Oct 2023
Security only
Oct 2023 – Apr 2025
EOL
Apr 30, 2025 ✕

Node.js 18 entered its Active LTS phase in October 2022 and moved to security-maintenance-only in October 2023. The OpenJS Foundation ended all support on April 30, 2025. No further patches will be released for any CVE, regardless of severity.

Running Node.js 18 past end of life?
The good news: extended support for Node.js 18 exists — vetted vendors ship security patches for years past the official date. Right now that coverage spans Node.js 18 12, 14, 16, 18, 20, with 210+ post-EOL CVE fixes documented in vendor release notes. Tell us where to reach you and we’ll reply with matched options and pricing guidance — or an honest “no vendor covers this.” Free, no obligation.

Free · No obligation · Independent — we track the dates, vendors don’t pay for placement · dates verified against vendor sources. See all support options →

Which vendors offer extended CVE patches for Node.js 18?

Node.js 18 still has a commercial patch path. The Node.js project's own end-of-life notice points users who cannot upgrade to commercial post-EOL support, and as of October 2026 at least two extended lifecycle support vendors list Node.js 18 among the versions they patch. What each vendor publishes about scope differs, so get the terms in writing before you buy:

Third-Party ELS Vendors

Extended Lifecycle Support

Specialist ELS vendors cover Node.js as part of broader extended support for end-of-life open-source software. Severity scope, patch turnaround and contract length are set by each vendor; ask for all three in writing.

View via endoflife.ai →

Feature comparison

Vendor CVE patching Compliance docs Multi-year contracts Other EOL runtimes
Third-party ELS vendors ✓ severity scope varies by vendor Varies by vendor Ask the vendor PHP, Python, Java and .NET; some also cover EOL Linux distributions

Migrate or extend? How to decide

Choose migration if your Node.js 18 application can be moved to Node.js 22 or Node.js 24 within 6–12 months without major breaking changes. Both are LTS lines: Node.js 22 has security support until April 30, 2027, and Node.js 24, which entered LTS on October 28, 2025, has it until April 30, 2028. Migration eliminates ongoing support costs.

Choose extended support if migration is blocked by: third-party dependency incompatibilities, regulatory change-freeze periods, insufficient engineering bandwidth, or complex monorepos where upgrading the runtime requires months of testing.

ELS is a bridge — not a destination. The right answer is always to establish a migration timeline alongside any extended support contract.

Check your full EOL exposure

See which vendors cover every EOL component in your stack — not just Node.js 18.

Open CVE Intelligence Tool →
What to do about it

Node.js currently carries an EOL Risk Score™ of 80/100 — Grade D, critical risk, recalculated at every site build from EOL recency, attack surface, CISA KEV exposure, and extended-support availability. Per-version scores and dates are on the Node.js lifecycle page.

The right response comes down to one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support fees paid repeatedly cost more than doing the project once. Indefinitely, migrate now and plan the next one before it surprises you. Extended support is often the more expensive choice over a multi-year horizon — a bridge, not a destination. And if this deadline feels like vendor caprice, it isn’t — why end of life is inevitable for every version, with the receipts.

Guides: Node.js 18 migration guide

Frequently asked questions

Is Node.js 18 still supported?
No. Node.js 18 reached its official end of life on April 30, 2025. It no longer receives security patches, bug fixes, or CVE remediation from the OpenJS Foundation. Organizations still running Node.js 18 in production are exposed to any vulnerability disclosed after that date.
Which vendors offer extended security support for Node.js 18 after end of life?
As of October 2026, at least two extended lifecycle support (ELS) vendors list Node.js 18 among the versions they patch, and the Node.js project itself points users who cannot upgrade to commercial post-EOL support. Vendors differ in severity scope, patch turnaround, compliance documentation and contract terms. See the vendor directory for current options.
What are the risks of running Node.js 18 past its EOL date?
Any CVE disclosed after April 30, 2025 falls outside the upstream project's patch policy. Vulnerability scanners may stop flagging issues against EOL versions, creating a false sense of security. Compliance frameworks including SOC 2, PCI DSS, and ISO 27001 typically require running supported software.
What version of Node.js should I migrate to?
Node.js 24 and Node.js 22 are both LTS lines and both are valid migration targets. Node.js 24 has security support until April 30, 2028; Node.js 22 until April 30, 2027. Node.js 20 is not a target: it reached end of life on April 30, 2026. Choose based on your ecosystem's compatibility with each version; 24 gives the longer runway.
How long does extended support for Node.js 18 last?
Duration depends on the vendor. The vendors that list Node.js 18 market their support as open-ended while the subscription runs; contract length and renewal terms come from each vendor's quote. Pair any contract with a migration plan rather than treating it as permanent.

The Monthly EOL Digest™

Once a month — critical EOL dates, CVE blind spots, and lifecycle changes worth knowing about.