EOL Next.js Security Patches — Versions 12, 13.5 & 16

Check the status of CVEs. Learn More.

 CVE Status (opens in new tab)

php2shell patches (CVE-2026-109618 and CVE-2026-109619) for EOL PHP are out now. With sales replies slower than usual due to high demand, the fastest route to patched packages is to buy ELS for Runtimes online (opens in new tab). Read the patch FAQ

TuxCare keeps you ahead of threats by proactively tracking and patching new CVEs impacting Next.js. View all security fixes available to date here.

Keep Running.
Skip the Risks.

Upgrading end-of-life open-source runtimes, libraries, and
applications can be disruptive, resource-intensive, and costly.

TuxCare’s ELS keeps your legacy and EOL
components secure, compliant, and stable – without
the risks of costly upgrades.

What Does Endless Lifecycle Support Include?

Rapid CVE Response

Rapid SLA-backed security patches for Next.js for as long as you need

Complete Coverage

Security fixes for both direct and transitive dependencies in Next.js AT NO EXTRA COST

Preserved Compatibility

Extensively tested updates designed to work flawlessly with your existing code

Seamless Integration

Plug-and-play integration with your existing workflows and CI/CD pipelines

Secure Distribution

Signed, tamper-proof Next.js security updates delivered from trusted, TuxCare-hosted repositories

Trusted Support

24/7 expert assistance with Next.js vulnerability triage, security patch requests, and troubleshooting

Secure Every Layer of Your OSS
Dependency Tree for the Long Run

End-of-life risk rarely lives in your top-level packages. It hides in the transitive
dependencies woven throughout your open-source stack.

When one of those libraries becomes vulnerable, every downstream component
must be rebuilt and validated.

TuxCare automates this entire process – tracking vulnerable EOL
libraries, applying security fixes, and rebuilding dependent components
– ensuring your full dependency chain stays secure and stable.

How Does It Work?

1

We onboard new projects and enable 24/7 automated CVE tracking – monitoring the NVD, vendor, and GitHub security advisories, and other sources.

2

Once CVEs are detected, we backport upstream fixes using algorithmic and AI-assisted automation, with expert validation to ensure accuracy.

3

Patches are compiled in a binary format, extensively tested (for integrity, functionality, and regression), signed, and deployed to ELS repositories.

4

Your package managers, build tools, or orchestrators check for updates, then automatically pull and install them.

Learn More

Built for Your Stack

ELS for Next.js is built to install easily and run with your existing workflows

TuxCare has successfully resolved

more than 14,000 CVEs

in open-source software - keeping enterprise
systems secure and compliant

Check It Out

We’ve Been Powering Enterprise-Grade Patching At
Unprecedented Scale – and We're Just Getting Started

2,700+
Enterprise Clients

70,000+Packages Curated

420,000+
Patches Delivered

14,000+
Vulnerabilities Fixed

11,000+
Kernels Supported

70+
Linux Distro Versions Supported

Why TuxCare?

15 years of proven excellence in open-source patching have created highly
automated processes and systems, providing:

Extensive Coverage of Open-Source Technologies

We provide long-term security across your entire stack, supporting a wide and continually expanding set of open-source projects, libraries, and runtimes – all from a single, trusted partner.

Efficiencies in Build Chains and Testing

We utilize advanced automation across CVE discovery, backporting, building, and release workflows to accelerate delivery and ensure the highest possible quality of security patches.

Identification and Patching of Transitive Dependencies

We go beyond surface-level scanning to uncover and fix hidden vulnerabilities deep in your dependency trees, securing the entire software supply chain with precision and scale.

Fast and Consistent Delivery of Patches with Supporting SLAs

Automated pipelines and mature workflows ensure rapid, reliable patch delivery backed by SLAs – giving you confidence in your risk management and compliance posture.

Frequently Asked Questions

Not long. Next.js ships majors roughly annually, concentrates fixes on the current release, and backports to older majors only selectively. With no published LTS policy, a two-year-old Next.js application is effectively unsupported. ELS for Next.js gives EOL majors a defined patching commitment.

Not reliably — and Next.js vulnerabilities skew severe, because the framework sits at the intersection of server execution, authentication, and routing. The December 2025 RSC cluster made the point: the React2Shell RCE (CVE-2025-55182, CVSS 10.0) hit Next.js 15.x and 16.x, and the follow-on denial-of-service and source code exposure flaws reached every App Router line from 13.3 on. For those older lines, upstream's remediation was "upgrade to 14.2.35," not a patch for the version you run.

Next.js 12.3.7, 13.5.11, 14.2.35, and 16.0.6 — baselines that map to the patched release lines from the 2025 RSC advisories. Other versions are available on request.

Because the framework changes, not just the library. Major versions have moved from Pages Router to App Router, changed caching and revalidation defaults, reworked next/image and middleware, and coupled tightly to specific React versions. An upgrade is an application rewrite in miniature.

Yes, and it matters here more than anywhere. Next.js and React are separate packages with tight compatibility requirements, and the RSC CVEs originated in React itself. ELS for React runs alongside Next.js so both layers stay patched without breaking the version coupling.

Patched packages come from TuxCare's npm registry as @els-js/next, aliased in package.json or configured by the TuxCare Patcher; next build and next start are unchanged. TuxCare targets 14 days from disclosure for CVSS 7.0+ CVEs, 60 days for medium, and 90 days for low, with SBOM and VEX data per release.

Talk to a TuxCare Expert

Tell us your challenges, and our experts will help you find the best approach to address them with the TuxCare product line.

Ask Us a Question