NEXT.JS COVERAGE

Next.js 14 is end of life. Your patching does not have to be.

Next.js extended support from OSSeva: Next.js 14 reached end of life on 26 October 2025, and recent high-severity CVEs such as CVE-2026-44573 and CVE-2026-64645 list 14.x as affected but are fixed only on 15.5 and later. OSSeva patches Next.js 14 after end of life and assesses other versions case by case. Critical fixes ship within 48 hours and High within 7 days.

Who it is forTeams running Next.js 14 that cannot take React 19 and the Next.js 15 changes yet
What you getA patched Next.js 14 build as a drop-in package, with a documented patch history. Assure adds an upgrade path assessment and 24/7 reactive support.
How it is pricedPer application, not per developer or per route. Ask for a quote.
What happens nextYou send your work email, we confirm your Next.js version, router and hosting, and you get a coverage plan.

Reply within 1 business day · No commitment · or book a 15-minute call

Last reviewed

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

Trusted globally by enterprises

NokiaSquareLittle CaesarsPanasonic ConnectPaylocity

Next.js support windows

Vercel's support policy keeps a major in Active LTS until the next major ships, then in Maintenance LTS for two years after its 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 that in rare circumstances Vercel patches versions outside the policy; 14.2.35 (December 2025) came after the 26 October 2025 end date. Read on 19 November 2026.

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

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

Next.js support policy (nextjs.org) →Next.js EOL dates for every version →

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. The exposure column is from the CVE description: the flaw applies only when that feature is in use. This is a sample of 2026 advisories, not a complete list.

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

GitHub advisory for CVE-2026-44573 →GitHub advisory for CVE-2026-44578 →GitHub advisory for CVE-2026-64645 →

What a move from Next.js 14 to 15 involves

Migration is often the right long-term answer. OSSeva sells patches, not rewrites, so these are the facts from the Next.js upgrade guide to size the project honestly.

  • React 19: the Next.js 15 upgrade guide sets react and react-dom 19 as the minimum, so a Next.js upgrade is also a React upgrade (see the React hub for what that involves).
  • Async request APIs: cookies, headers, draftMode, and params and searchParams in pages and layouts become asynchronous, a breaking change that the @next/codemod upgrade command automates in part, with a temporary synchronous fallback.
  • Support window: Next.js 15 itself has security releases only through 31 January 2027, so the realistic targets are 15 as a stepping stone or 16 directly.

React extended support →Node.js extended support, since Next.js runs on Node.js →

Why now

Next.js 14 reached end of life on 26 October 2025

Vercel's support policy gives each major two years of Maintenance LTS after its release and lists 14.x as unsupported. endoflife.date dates the end of life at 26 October 2025, and 14.2.35 (December 2025) was the last release.

Next.js 15 follows on 31 January 2027

Vercel extended Maintenance LTS for Next.js 15 beyond its original end date of 21 October 2026 and now promises security releases through 31 January 2027. Teams that move from 14 to 15 face the same decision again on that date.

Next.js 14 is inside the range of recent high-severity CVEs

Five CVEs published between May and October 2026 list a range that includes 14.x and are fixed only on 15.5.x and 16.x. The table below gives each with its fixed version.

Versions covered

All versions below receive active CVE patches from OSSeva. Version numbers in monospace are exact release identifiers.

VersionStatusActive CVEs
14(Community EOL 26 Oct 2025, last release 14.2.35)EOLClean
Next.js end of life dates for every version →

Running a Next.js version or build not listed here?

What you get

Three tiers — pick the level of engagement that matches your team's operational needs and compliance requirements.

OSSeva Patch

Security patches for Next.js 14 after end of life.

  • Backported security fixes for Next.js 14
  • Critical CVEs fixed within 48 hours, High within 7 days
  • Signed artifacts (GPG + Sigstore)
  • CVE disclosure notifications
  • Architecture review
  • 24/7 managed operations
Most popular

OSSeva Assure

Patch plus compliance documentation and upgrade planning.

  • Everything in Patch
  • SOC 2 / HIPAA attestation package
  • Next.js upgrade path assessment
  • 24/7 reactive support

OSSeva Operate

Full MSP: 24/7 monitoring, 15-min P1 response, named engineers.

  • Everything in Assure
  • 24/7 application and runtime monitoring
  • 15-minute P1 incident response SLA
  • Named senior engineer on your account

All tiers priced per cluster/application — not per core.

Compliance library

📄SOC 2 compliance evidence package
Request →
📄Sample Audit Narrative
Request →
📄Pen-Test Report Summary
Request →
📄HIPAA Technical Safeguard Matrix
Request →

Questions

Frequently asked questions

Book a 15-minute call

Which Next.js versions does OSSeva patch?

Next.js 14 after end of life. Other versions are assessed case by case through a version coverage check.

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.

How fast are Next.js vulnerabilities patched?

Critical vulnerabilities (CVSS 9.0 or higher) within 48 hours and High within 7 days. Everything else goes into a scheduled batch.

Does OSSeva upgrade Next.js applications to 15 or 16?

No. OSSeva sells security patches for the Next.js version you run. Moving to 15 or 16 is often the right long-term step, and Assure includes an upgrade path assessment, but the upgrade work stays with your team.

How is OSSeva Next.js support priced?

It is priced per application. Request a quote and a senior engineer replies within 1 business day.

Get a quote

Ready to get Next.js patched and supported?

Tell us your Next.js versions and an engineer replies within 1 business day with coverage and a price. Prefer a call? It takes 15 minutes.

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

Prefer to talk or read more first?

Book a call