What the November 3 release fixed
On November 3, 2026 the Next.js team published its November 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 when the same public
use cachefunction is called both directly and from insideunstable_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 cachefunctions 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 cachefunction 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, 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: 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 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. 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.





