Back to insights
Software Development6 min read

Next.js 16.4.5 November Security Release: The use cache Leak and Six More Flaws, What to Do

On 3 November Next.js shipped 16.4.5 and 15.5.29, fixing seven vulnerabilities: one high and six medium severity. What does it mean for multi-tenant apps using cache components, self-hosted deployments and Edge routes?

By , Founder, Aktaş Digital
Next.js 16.4.5 November Security Release: The use cache Leak and Six More Flaws, What to Do

In brief: The Next.js team published its scheduled security release on 3 November 2026: v16.4.5 (Active LTS) and v15.5.29 (Maintenance LTS). It fixes seven issues: one high and six medium severity. The most serious (GHSA-mfr8-8qww-v76h) applies when Cache Components are enabled, the same public use cache function is called both directly and from inside unstable_cache, and the function reads a root parameter (for example a tenant identifier): another request's result can be served to the wrong caller. The rest cover nested use cache, binary arguments, cache poisoning and response framing in self-hosted (next start) apps, a HttpOnly cookie value showing up in an internal header on Edge routes, and an SVG-rejection bypass in image optimisation. Upgrade with npm install [email protected] (or [email protected] on the 15 line). This article is based on the official Next.js announcement.

Last updated: 9 November 2026

What happened?

A week earlier the Next.js team had announced an upcoming security release. The patches shipped on 3 November. According to the official post, seven items matter:

SeverityIssueWho is concerned
HighCross-tenant cache disclosure when combining unstable_cache and use cache (GHSA-mfr8-8qww-v76h)Cache Components on; a public use cache function reads a root parameter
MediumCross-root-parameter disclosure in nested use cache functions (GHSA-vc7v-qv4w-wrv8)Cache Components + nested use cache
MediumCross-user cache disclosure and poisoning through binary use cache arguments (GHSA-rhh4-g77r-r9qj)Apps passing security-significant binary arguments to use cache
MediumShared shell cache poisoning in self-hosted appsnext start + Cache Components, Partial Prefetching off or unset, a specific route shape
MediumCross-client response injection via stale compressed response framing (GHSA-pc58-hwjq-p385)Self-hosted apps returning an attacker-controlled fetched Response unchanged; specific HTTP/1.1 reverse-proxy behaviour
MediumCookie values exposed in the x-middleware-set-cookie header on Edge routes (GHSA-f3mh-rxg3-f5g2)Edge Route Handlers / Edge API routes using NextResponse.cookies.set()
MediumSVG rejection bypass in Image Optimization (GHSA-7qx7-33qx-rqx2)Attacker-controlled image from a permitted source; native image backend that can decode SVG

The serious one: cross-tenant cache disclosure

The technical conditions in the announcement are specific. Your app has Cache Components enabled, a 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, a concurrent call can receive another request's result without the root parameters being checked. That result can then be stored and served to later callers with the same arguments until it is revalidated or evicted. Where root parameters separate tenants, the result can contain another tenant's data.

So the risk is not for “every Next.js site” but for multi-tenant apps, or apps that use root parameters per language/site, and that have adopted the newer caching features. A simple corporate brochure site usually falls outside these conditions; upgrading is still cheap and quick.

The other six, briefly

  • Nested use cache: If an inner function reads a root parameter and returns an early value while the outer function finishes without waiting for a slower value, content generated for one parameter value can be served for another (tenant-, site- or locale-specific). The attacker does not inject content; the app's own content is reused in the wrong place.
  • Binary arguments: Distinct binary arguments can produce the same cache identity. If you distinguish users or accounts by them, a caller can receive another user's cached result or have their own served to someone else. It does not give access to unrelated cache entries.
  • Shared shell poisoning (self-hosted): An unauthenticated crafted URL can cause request-specific values to be stored in a page shell used by other URLs, giving wrong content or persistent 404s. The affected route shape is quite specific; configurations with Partial Prefetching enabled were not affected in the reported tests.
  • Response framing: Self-hosted apps that return an attacker-controlled fetched Response unchanged can forward decompressed bytes with the original compressed framing headers. Behind an HTTP/1.1 reverse proxy that queues pipelined requests on a shared backend connection, responses can be assigned to the wrong clients. It does not apply to every proxy setup.
  • Edge cookies: Even when marked HttpOnly, the cookie value could appear in x-middleware-set-cookie, which same-origin JavaScript can read. Impact needs a sensitive cookie on an affected response and attacker-controlled JavaScript on the same origin; it is not an independent way to run JavaScript. Node.js Route Handlers and cookies().set() were not affected.
  • SVG bypass: An attacker-controlled image from a permitted source can be misclassified as AVIF and bypass images.dangerouslyAllowSVG: false, letting the backend decode the original bytes as SVG. The source allowlist still applies; the finding does not itself demonstrate XSS or remote code execution, but it raises exposure to SVG parser resource exhaustion or decoder bugs.

What to do: 6 steps

  1. Find your version: the next version in package.json and the lockfile. The 16.4.1 or 15.5.28 we recommended in October is no longer enough (our October update article).
  2. Upgrade: npm install [email protected] (16.4 line) or npm install [email protected] (15.5 line). If you use pnpm or yarn, update the lockfile too.
  3. If you are on 16.4.4, move to 16.4.5 anyway: the team shipped 16.4.4 a day earlier only to backport bug fixes; the security fixes are in 16.4.5.
  4. Review your cache usage: search the code for use cache, unstable_cache and functions that read root parameters. If you separate tenant, language or site data, deploy after the upgrade and refresh the cache so old entries are gone.
  5. If you self-host (next start, Docker), review your reverse-proxy behaviour (HTTP/1.1 pipelining, response queuing) and rebuild your image.
  6. If you set cookies on Edge routes, verify with browser tools after the patch that sensitive cookies no longer appear in response headers.

Ask your software team for these checks in writing: which version you run, when the upgrade happened and the test results.

Why so many updates?

Two critical RCEs on 14 October, seven more issues on 3 November: new caching and server features in modern frameworks evolve fast and new surfaces get scrutinised fast. The price is maintenance that must be planned with version tracking in mind; see our maintenance and SLA guide and tech stack article. For general application security, see our 12 OWASP-focused measures.

Maintenance with Aktaş Digital

In Next.js projects we set up version tracking, patching and testing routines. To have your site or application reviewed, use our quote form. Related services: web applications and SaaS platform development.

Frequently Asked Questions

Are all Next.js sites affected by these flaws?

No. Most depend on specific conditions such as Cache Components, use cache or self-hosting. Your software team can tell from your code which conditions apply; moving to the patched version is still the safest path.

Are apps hosted on Vercel affected?

The announcement does not say per item how hosting changes things; only two items stress “self-hosted applications.” Update the dependency regardless of where you host.

I use Next.js 14 or 13. What now?

The announcement lists patches only for 16.4.5 and 15.5.29. If you are on older versions, plan a move to a supported line.

Will the upgrade break my site?

Patch releases carry small changes; still, try it first in a staging environment and test the build, home page, forms, images and session flows.

Has exploitation been reported?

The announcement does not report exploitation in the wild. That can change, and waiting gains you nothing.

Conclusion

Next.js 16.4.5 and 15.5.29 close seven flaws, mostly tied to caching and self-hosting scenarios. Priority is high for multi-tenant apps or those using the newer caching features, and the upgrade is cheap for everyone else. The first thing to do today: ask your software team, in writing, for your next version and the upgrade date.

#Next.js
Your first consultation is free
Let's bring your project to life
Tell us about your idea and we'll prepare a tailored roadmap and cost estimate.