Next.js EOL: end-of-life dates for every Next.js version

Next.js 14 reached end of life on 26 October 2025, and its last release was 14.2.35 in December 2025. Next.js 15 is in Maintenance LTS, with security releases through 31 January 2027, a date Vercel extended from 21 October 2026. Next.js 16 is Active LTS. OSSeva patches Next.js 14 after end of life. Dates checked against nextjs.org and endoflife.date on 19 November 2026.

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

Latest release
16.4.6
Supported lines
2
End-of-life lines
6
Next end of life
15 · 31 Jan 2027

Next.js 14 has ended; 15 is next

Upgrade, or keep Next.js 14 patched

Most applications should move to Next.js 16, or to 15 as a stepping stone. When React 19 or the Next.js 15 changes hold a site on 14, OSSeva patches Next.js 14. Other Next.js versions are assessed case by case. Critical fixes ship within 48 hours and High within 7 days.

Who patches Next.js after end of life

OSSeva provides Next.js extended support: patched, signed builds for Next.js 14 after upstream support ends, plus 24/7 operations on the Operate tier.

Next.js release timeline

Security SupportToday

All Next.js versions, release dates and end-of-life dates

VersionReleasedSecurity SupportLatestOSSeva
16 (LTS)1 year and 1 month ago(22 Oct 2025)Yes16.4.6–
15 (LTS)2 years and 1 month ago(21 Oct 2024)Ends in 2 months(31 Jan 2027)15.5.29–
14 (LTS)3 years and 1 month ago(26 Oct 2023)Ended 1 year and 1 month ago(26 Oct 2025)14.2.35 Patched
134 years and 1 month ago(25 Oct 2022)Ended 1 year and 11 months ago(21 Dec 2024)13.5.11–
125 years and 1 month ago(26 Oct 2021)Ended 4 years ago(21 Nov 2022)12.3.7–
115 years and 5 months ago(15 Jun 2021)Ended 4 years and 10 months ago(27 Jan 2022)11.1.4–
106 years and 1 month ago(27 Oct 2020)Ended 5 years and 5 months ago(15 Jun 2021)10.2.3–
97 years and 4 months ago(8 Jul 2019)Ended 6 years and 1 month ago(27 Oct 2020)9.5.5–

Lifecycle data from endoflife.date (MIT licence), refreshed 21 Nov 2026. “Patched” marks end-of-life lines OSSeva ships signed, backported builds for.

Next.js support windows: Active LTS and Maintenance LTS

Vercel's support policy keeps a major in Active LTS until the next major ships, then in Maintenance LTS for two years after the major's release, with only critical bug fixes and essential security updates. Maintenance LTS updates land as semver-minor releases even when they are breaking. The policy also says Vercel will patch versions outside it in rare circumstances, and 14.2.35 (December 2025) came after the 26 October 2025 end date.

Sources: nextjs.org/support-policy and endoflife.date, read on 19 November 2026.

VersionReleasedStatus on nextjs.orgEnd of life
Next.js 16Oct 2025Active LTSNo end date yet
Next.js 15Oct 2024Maintenance LTS31 Jan 2027 (extended from 21 Oct 2026)
Next.js 14Oct 2023Unsupported26 Oct 2025; last release 14.2.35

Next.js 13 and older are also listed as unsupported on the support-policy page.

Next.js CVEs that list 14.x and have no 14.x fix

Each CVE below was checked on cveawg.mitre.org and in the GitHub advisory on 19 November 2026. Both give an affected range that includes 14.x and name fixed versions only on 15.5.x and 16.x, so a Next.js 14 application stays exposed unless it upgrades or takes patches from elsewhere. The exposure column is from the CVE description: each flaw applies only when that feature is in use. This is a sample of 2026 advisories, not a complete list.

Affected-from versions and fixes from the CVE records and GitHub advisories.

CVEWhat it isExposureSeverityAffected fromFixed in
CVE-2026-44573Middleware authorization bypass through locale-less /_next/data requestsPages Router with i18n and middleware-based authorizationHigh (7.5, CVSS 3.1)12.2.015.5.16, 16.2.5
CVE-2026-44578Server-side request forgery through crafted WebSocket upgrade requestsSelf-hosted apps on the built-in Node.js server (not Vercel-hosted)High (8.6, CVSS 3.1)13.4.1315.5.16, 16.2.5
CVE-2026-64645Server-side request forgery or open redirect through rewrites() and redirects()A rule that builds its external hostname from request inputHigh (8.3, CVSS 4.0)12.0.015.5.21, 16.2.11
CVE-2026-64641Denial of service through excessive CPU useApp Router with at least one Server ActionHigh (8.2, CVSS 4.0)13.0.015.5.21, 16.2.11
CVE-2026-94482Denial of service through excessive CPU useApp Router with at least one Server ActionHigh (8.2, CVSS 4.0)13.0.015.5.28, 16.4.1

Next.js 14 did receive earlier security fixes after its release, for example 14.2.25 for CVE-2025-29927, so the 14 line was patched while it was supported. The CVEs above were published after the end date.

Who patches Next.js after end of life?

HeroDevs and OSSeva both sell security patches for Next.js versions Vercel no longer fixes. The table lists what each says, with HeroDevs' row taken from its own Next.js page, read on 19 November 2026.

Facts from each provider's own page, read on 19 November 2026. Nothing here comes from a third party.

ProviderNext.js versions the page listsFix timing the page states
HeroDevs (NES for Next.js)Its FAQ says NES for Next.js supports 12.3.5FAQ says security issues are top priority and fixed the same day where possible; SLA on request
OSSeva14 after end of life. Other versions case by caseCritical within 48 hours, High within 7 days

How we compared: HeroDevs' row uses only its own Next.js page, read on 19 November 2026; it lists CVEs by affected range but names 12.3.5 as the supported version, so confirm 14 with HeroDevs if you rely on it. Where HeroDevs is the better fit: an application on Next.js 12.3.5, which OSSeva does not name.

Upgrade Next.js 14 to 15 or 16, or keep patching 14?

Upgrade when you can, and note that 15 is itself in Maintenance LTS until 31 January 2027. The Next.js 15 upgrade guide sets react and react-dom 19 as the minimum, and makes cookies, headers, draftMode and the params and searchParams props asynchronous, a breaking change that the @next/codemod upgrade command handles in part. So a move from 14 is also a React upgrade, which is why many teams defer it.

Keep 14 patched when React 19 compatibility of your component libraries, or a release freeze, holds the application where it is. Patching keeps the 14.x CVEs above from sitting open in your scanner while you plan the move.

Running an end-of-life Next.js version?

OSSeva keeps end-of-life Next.js patched with signed builds and backported CVE fixes, documents it for your auditor, and can run it for you, so the upgrade happens on your schedule rather than the project’s.

Next.js extended support

Questions

Next.js end of life: common questions

Book a 15-minute call

Is Next.js 14 end of life?

Yes. endoflife.date lists 26 October 2025, and Vercel's support policy lists 14.x as unsupported. 14.2.35, published in December 2025, was the last release. OSSeva patches Next.js 14 after end of life.

When does Next.js 15 reach end of life?

31 January 2027. Vercel extended Maintenance LTS for Next.js 15 beyond its original end date of 21 October 2026 and says it will keep publishing security releases through 31 January 2027.

Is Next.js 13 end of life?

Yes. Vercel's support-policy page lists 13.x, and every older major, as unsupported.

Does Next.js have LTS?

Yes. Vercel's policy gives each major Active LTS until the next major ships, then Maintenance LTS for two years after its release, with only critical bug fixes and essential security updates in that second phase.

Which Next.js versions are still supported?

Next.js 16 (Active LTS) and Next.js 15 (Maintenance LTS, security releases through 31 January 2027), per nextjs.org/support-policy. Every older major is listed as unsupported.

Who provides Next.js support after end of life?

Vercel stops regular fixes at end of life, though it says it patches outside the policy in rare circumstances. Third-party providers fill the gap. OSSeva patches Next.js 14 after end of life, and HeroDevs' own page names 12.3.5.

What is the latest Next.js version?

16.4.6, released 9 Nov 2026, on the 16 (LTS) line. Other supported lines: 15.

When is the next Next.js end of life?

Next.js 15 reaches the end of security support on 31 Jan 2027. After that date the project stops shipping security fixes for 15, and CVEs disclosed later stay unpatched upstream.

Can I get security patches for an end-of-life Next.js version?

Yes. OSSeva ships signed builds with backported CVE fixes for Next.js 14 after upstream support ends, on the Patch, Assure and Operate tiers, so you can stay on the version you run while you plan the upgrade.

Get a quote

Still running an end-of-life Next.js?

Tell us the versions and the estate size. We will tell you whether to upgrade or keep it patched, and what each costs.

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

Prefer to talk or read more first?

Book a call