# Next.js November 2026 security release: what to patch

URL: https://intelligizedigital.com/blog/nextjs-november-2026-security-release-cache-leaks/
Updated: 2026-11-20
Summary: Next.js 16.4.5 and 15.5.29, released November 3, 2026, fix seven vulnerabilities. The high severity one can serve one tenant's cached data to another when use cache and unstable_cache are combined. Multi-store, multi-locale and B2B headless storefronts should upgrade first and then check caching by tenant.

[Node.js and JavaScript](https://intelligizedigital.com/blog/?topic=node-js-and-javascript)

## Next.js November security release fixes cross-tenant cache leaks

Next.js 16.4.5 and 15.5.29, released November 3, 2026, fix seven vulnerabilities, most of them in Cache Components and use cache. The high severity issue can serve one tenant's cached data to another. For multi-store, multi-locale and B2B storefronts that split content by route parameter, this patch deserves priority.

**In short:** Next.js 16.4.5 and 15.5.29, released November 3, 2026, fix seven vulnerabilities. The high severity one can serve one tenant's cached data to another when use cache and unstable_cache are combined. Multi-store, multi-locale and B2B headless storefronts should upgrade first and then check caching by tenant.

21 November 2026 Intelligize Digital
4 min read [All notes](https://intelligizedigital.com/blog/)

### Key points

- Next.js 16.4.5 and 15.5.29, released November 3, 2026, fix one high and six medium severity vulnerabilities.

- The high severity flaw can disclose cached content across root-parameter values, such as tenant identifiers, when use cache and unstable_cache are combined.

- Next.js moved to a roughly monthly, pre-announced security release program in July 2026.

- Next.js reports 51 security advisories in 2026 so far, up from 14 in 2025 and 6 in 2024.

### On this page

- What the November 3 release fixed

- Why multi-store and B2B storefronts should patch first

- Security releases now arrive about once a month

- Built-in version warnings from Next.js 16.4

- What we would do this month

Not answered here? Ask on the free 30-minute audit call.

[Book a free audit](https://intelligizedigital.com/free-audit/)

### What the November 3 release fixed

On November 3, 2026 the Next.js team published [its November security release](https://nextjs.org/blog/november-2026-security-release), with patches in v16.4.5 (Active LTS) and v15.5.29 (Maintenance LTS). It fixes one high and six medium severity issues. Most of them involve Cache Components and the `use cache` directive:

- High: [cross-tenant cache disclosure](https://github.com/vercel/next.js/security/advisories/GHSA-mfr8-8qww-v76h) when the same public `use cache` function is called both directly and from inside `unstable_cache`, and the function reads a root parameter such as a tenant identifier. During a cold cache fill, one request can receive another request’s result, which is then stored and served to later callers.
- Medium: nested `use cache` functions can serve content generated for one root-parameter value to requests for another. The advisory names tenant, site and locale content as what can cross over.
- Medium: distinct binary arguments to a `use cache` function can produce the same cache identity, so one user can receive another user’s cached result.
- Medium: Edge route handlers that set cookies with `NextResponse.cookies.set()` can [expose the cookie in an internal response header](https://github.com/vercel/next.js/security/advisories/GHSA-f3mh-rxg3-f5g2), where same-origin JavaScript can read it even when the cookie is HttpOnly.
- Medium: three issues for self-hosted apps, covering shared shell cache poisoning under `next start`, response framing behind some HTTP/1.1 reverse proxies, and an SVG rejection bypass in Image Optimization.

### Why multi-store and B2B storefronts should patch first

Root parameters are how many headless builds keep stores apart. A brand that runs a UK and a US store from one Next.js app, or a B2B storefront that splits catalogs by customer group, often puts the store, locale or account segment in the top route segment and reads it inside cached data functions. The first two bugs match that pattern, and the result is one segment’s content showing up for another.

In our view the risk is highest where prices or availability differ by segment. If contract pricing passes through a shared cache, a buyer could see a price list meant for another account. We would keep customer-specific pricing out of public `use cache` functions entirely, patched or not.

The cookie issue matters for storefronts that set session or cart cookies in Edge route handlers. The advisory says it needs attacker-controlled JavaScript already running on the same origin, for example through a compromised third-party script, and is not a way to run JavaScript by itself. Node.js route handlers and routes using `cookies().set()` were not affected in the reproduction.

### Security releases now arrive about once a month

This was a scheduled release. In July the team [announced a formal security release program](https://nextjs.org/blog/next-security-release-program): roughly once a month it posts advance notice with the expected date and the highest severity, and it still ships ad hoc patches for urgent or actively exploited issues. The [Next.js blog](https://nextjs.org/blog) shows scheduled releases on August 25, September 30 and November 3, plus out-of-band updates for upstream dependency issues on September 22 and October 14.

On November 17 the team [explained the rise in advisories](https://nextjs.org/blog/how-were-using-ai-to-make-nextjs-more-secure). It counts 6 advisories in 2024, 14 in 2025 and 51 so far in 2026, and says 70 percent of this year’s issues were in code at least a year old, with 43 percent in code three years or older. It credits AI-assisted research for finding them, and says many of the most serious issues came from upstream dependencies such as image libraries.

### Built-in version warnings from Next.js 16.4

The same post says that from Next.js 16.4, `next dev` and `next build` warn when the installed version is affected by a known vulnerability, and DevTools shows a prompt to upgrade. There is also `npx next@canary upgrade --agent`, which picks the latest safe release within the oldest major version that has a fix and hands the upgrade to a coding agent. That command runs from the canary channel, so we would run it on a branch and review the diff like any other pull request.

### What we would do this month

5 checks

- Upgrade to 16.4.5 or 15.5.29 or later. Those are the two lines the release patches, so an app on any other line needs a bigger move.
- Search the codebase for `unstable_cache` and `use cache`, and list every cached function that reads a root parameter or takes a user or account identifier.
- Find Edge route handlers that call `NextResponse.cookies.set()` for session, cart or auth cookies.
- If you self-host with `next start` behind a reverse proxy, read the three self-hosted advisories against your actual proxy setup.
- Follow the security posts on the Next.js blog and book a patch slot in the week after each scheduled release, outside any sale period.

Certifications

### Certifications and partner programmes

Intelligize Digital is a registered partner of these platforms and hosts.

- [Shopify Shopify Partner](https://intelligizedigital.com/partners/shopify/)
- [BigCommerce BigCommerce Partner](https://intelligizedigital.com/partners/bigcommerce/)
- [WP Engine WP Engine partner](https://intelligizedigital.com/partners/wp-engine/)
- [Automattic Automattic for Agencies](https://intelligizedigital.com/partners/automattic/)
- [Nexcess Nexcess partner](https://intelligizedigital.com/partners/nexcess/)
- [Hostinger Hostinger partner](https://intelligizedigital.com/partners/hostinger/)

- BigCommerce Certified
- **Liquid Storefronts for Theme Developers** Shopify Certified
- **Headless at Shopify for Developers** Shopify Certified
- **Shopify Foundations** Shopify Certified
