OSSeva Blog
OperationsUpgrade Node.js or Buy Third-Party Patches? A Decision Framework
Should you upgrade Node.js instead of buying third-party patches?
Upgrade unless a specific blocker stops you, and buy patches only for the services with one. Node.js 18 ended on 30 April 2025 and Node.js 20 on 30 April 2026, so neither gets upstream fixes. A patch subscription for the line you run is a bridge: Node.js extended support keeps it patched while the upgrade is finished, and does not replace it.
Running Node.js in production? OSSeva patches and supports it, end-of-life versions included.
Node.js extended support: what is coveredThe five questions to ask for each service
Answer them per service, not per company, because the answer changes from one service to the next.
| # | Question | If yes | If no |
|---|---|---|---|
| 1 | Do all native add-ons build on Node.js 24 or 26, and do the tests pass? | Upgrade | Go to 2 |
| 2 | Does a vendor certification or contract fix the Node.js version? | Patched builds until the vendor moves | Go to 3 |
| 3 | Does a release freeze cover the service before the next audit? | Patched builds until the freeze lifts, then upgrade | Go to 4 |
| 4 | Is the service internet-facing or does it handle regulated data? | Patch or upgrade now; do not wait | Go to 5 |
| 5 | Is the service due for retirement? | A documented exception may be enough | Upgrade |
A service that answers "upgrade" to question 1 should not be on patches at all. Most Node.js upgrades are a test run and a rebuild of native add-ons, which is why the upgrade guide is usually the cheaper path.
Which target version?
Go to 24 or 26, not 22, unless a small step is all the window allows. The dates, from the Node.js release schedule and endoflife.date, checked on 17 November 2026:
| Target | End of life | Consequence |
|---|---|---|
| Node.js 22 | 30 April 2027 | Under six months away; the work repeats |
| Node.js 24 | 30 April 2028 | Maintenance LTS since 20 October 2026 |
| Node.js 26 | 30 April 2029 | LTS since 28 October 2026; the longest runway |
What does the bridge need to be a bridge?
Patched builds need a recorded upgrade date for each service, a named owner and a review each quarter. Without those, the subscription becomes a permanent state, and the Node.js project describes commercial support for ended lines as a temporary solution. Ask vendors the questions in how to choose a Node.js extended support vendor, and price both sides with the upgrade vs extended support calculator.
Frequently asked questions
Is it safe to wait and upgrade later?
Only with a patch source in the meantime. Node.js 20 has missed four security releases since 30 April 2026, and each one adds findings that only an upgrade or a backported fix closes.
Should I upgrade Node.js 18 to 20?
No. Node.js 20 has also ended. Move to 24 or 26.
When is extended support the right call?
When a native add-on, a vendor certification or a release freeze holds the service, and you have a dated plan to leave.
Can I mix both?
Yes, and most estates do, service by service.
How this was checked
End dates are from the Node.js release schedule and endoflife.date on 17 November 2026. The count of missed releases is from the site's Node.js vulnerabilities by version tally. The decision table is a framework, not a benchmark.
Tags
Related articles
What It Costs to Patch Unsupported Node.js: Upgrade vs Extended Support
November 17, 2026OperationsHow to Choose a Node.js Extended Support Vendor: 12 Questions to Ask
November 17, 2026OperationsNES, ELS and Stay-Put Support for Node.js: How the Models Differ
November 17, 2026SecurityWho Provides Node.js Security Patches After End of Life? (Node 18 and 20)
October 6, 2026MigrationNode.js Version Upgrade: 18 and 20 to 22 or 24, Step by Step
October 5, 2026OperationsHow to Choose a PostgreSQL Extended Support Vendor
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?