Skip to Content
Cloud & DevOps

Next.js November 2026 Security Release: What to Patch and How to Upgrade Safely

Next.js 16.4.5 and 15.5.29 fix seven vulnerabilities, one rated high, mostly in caching. Here is who is affected and a safe upgrade checklist.

Nexgenex Labs ResearchBlog
PublishedReading time6 min read
Next.js November 2026 Security Release: What to Patch and How to Upgrade Safely

Photo: Markus Spiske · CC0 · Wikimedia Commons

The release

On 3 November 2026, the Next.js team released v16.4.5 (Active LTS) and v15.5.29 (Maintenance LTS) to fix seven vulnerabilities: one rated high and six medium. A follow-up 16.4.6 shipped on 9 November. If your site or app runs on Next.js, plan the upgrade this week.

npm install [email protected] (or the latest 16.4.x) for 16.x, and npm install [email protected] for 15.5.

Summary graphic: Next.js November 2026 Security Release: What to Patch and How to Upgrade Safely
In one image

Save it. Share it with your team.

The short version of this post, ready for your Instagram Story or feed.

What was fixed

IssueSeverityWho is affected
Cross-tenant cache disclosure combining unstable_cache and use cacheHighApps with Cache Components where a cached function reads a root parameter such as a tenant ID
Cross-root-parameter disclosure in nested use cache functionsMediumApps with nested cached functions that read root parameters
Cache disclosure and poisoning through binary use cache argumentsMediumApps that pass user-identifying binary arguments to cached functions
Shared shell cache poisoningMediumSelf-hosted next start with Cache Components and specific dynamic route shapes
Response injection through stale compressed response framingMediumSelf-hosted apps behind certain HTTP/1.1 proxies that return fetched responses unchanged
Cookie values exposed in an internal header on Edge routesMediumEdge route handlers that set cookies with NextResponse.cookies.set()
SVG rejection bypass in Image OptimizationMediumApps that rely on dangerouslyAllowSVG: false with a native image backend

The common theme is caching. Four of the seven issues can serve one user's or tenant's cached content to another. That matters most for multi-tenant SaaS, dashboards and anything with logged-in pages.

Am I affected?

  • Simple marketing sites that don't use Cache Components or Edge cookie handling are at lower risk, but should still upgrade: you don't want to audit seven edge cases by hand.
  • Multi-tenant SaaS using use cache with tenant or locale root parameters: upgrade first, then check for cached responses served across tenants.
  • Self-hosted apps (next start behind Nginx or another proxy) should take the proxy-related fixes seriously.

A safe upgrade checklist

  1. 01Read the advisory and note which issues match features you use.
  2. 02Upgrade next on a branch, and keep react and react-dom on the versions the release supports.
  3. 03Delete the .next folder and do a clean build to avoid stale cache artefacts.
  4. 04Run your type check, lint and tests, then click through logged-in, multi-tenant and image-heavy pages on a preview deployment.
  5. 05If you self-host, purge any shared cache (CDN or data cache) after deploying, so no poisoned entries survive.
  6. 06Deploy, then watch error rates and logs for a day.

How Nexgenex Labs can help

We build on Next.js every day, including this website. If you'd like us to patch and verify your app, or set up automated dependency updates so the next release is routine, talk to our team about maintenance and support.

Have a project like this in mind?

Talk To Our Team →
Newsletter

Insights toYour Inbox.

Join 15,000+ tech leaders receiving our weekly collection of breakthroughs and human stories.