On November 3, 2026 the Next.js team shipped a coordinated security release covering seven advisories. The fixes landed in two versions:
| Release line | Patched version | Support status |
|---|---|---|
| 16.x | 16.4.5 | Active LTS |
| 15.x | 15.5.29 | Maintenance LTS |
If you're on either line, upgrade first and read the rest later:
pnpm add next@16.4.5 # or next@15.5.29 on the 15.5 lineThe seven advisories at a glance
Most issues only bite when you use a specific feature. That's the useful way to read this release: find the features you actually use.
| # | Issue | Severity | Who should care |
|---|---|---|---|
| 1 | Cross-tenant cache disclosure (unstable_cache + use cache) | High* | Cache Components apps that call the same cached function directly and through unstable_cache |
| 2 | Cross-root-param disclosure in nested use cache | Medium | Nested cached functions that read root params (e.g. tenant or locale) |
| 3 | Cache disclosure/poisoning via binary arguments | Medium | Passing Blob or other binary args to a shared use cache function |
| 4 | Shared shell cache poisoning | Medium | Specific dynamic-route shapes with Cache Components and a blocking fallback shell |
| 5 | Cross-client response injection | Medium | Self-hosted apps returning a fetched Response unchanged behind an HTTP/1.1 proxy with pipelining |
| 6 | Cookie values exposed via an internal header | Medium | Edge Route Handlers / Edge API routes calling NextResponse.cookies.set() |
| 7 | SVG rejection bypass in Image Optimization | Medium | Built-in image optimizer with dangerouslyAllowSVG: false |
*The Next.js post rates #1 High; Netlify's changelog lists it as Medium. Treat it as High.
Cache Components is the common thread
Four of the seven advisories (#1–#4) involve Cache Components and the use cache directive. The pattern is similar each time: a cached value that depends on something request-specific — a root parameter like a tenant ID, or a binary argument — gets stored under a key that doesn't fully capture that dependency. The result is one user (or tenant) seeing another's cached output, or a valid page getting stuck behind a cached 404.
If you run a multi-tenant app where a root segment like app/[tenant] drives data, this is the release to prioritise.
Edge cookies (#6)
Cookies set with NextResponse.cookies.set() inside Edge route handlers were mirrored into an internal response header that same-origin JavaScript could read — even for HttpOnly cookies. Exploiting it requires attacker-controlled script on your origin, so it's an XSS amplifier rather than a standalone hole. Node.js route handlers and cookies().set() weren't affected.
Image Optimization (#7)
A crafted image from an allowed remote source could be misdetected as AVIF and slip past dangerouslyAllowSVG: false. Your remotePatterns allowlist still applies, and the advisory doesn't demonstrate XSS on its own — but it defeats a setting people rely on.
Does it affect your hosting?
Netlify published which advisories apply to its platform. In short, its isolated serverless invocations, its own response framing and its Image CDN rule out #1, #5 and #7 there — but #2, #3, #4 and #6 do apply, and the Middleware variant of #6 also needs @netlify/plugin-nextjs 5.16.6. After upgrading on Netlify, redeploy and purge cached responses; previews and branch deploys keep their own caches.
The official post doesn't spell out the impact on other hosts, so the safe assumption is: upgrade everywhere.
A quick checklist
- Check your version:
pnpm why next. Anything below16.4.5/15.5.29needs the upgrade. - Search your code for
use cache,unstable_cacheandcacheComponents. If you find them, upgrade and clear your data cache after deploying. - Search for
runtime = "edge"pluscookies.set(to see if #6 touches you. - If you self-host behind nginx/HAProxy with HTTP/1.1 keep-alive to the app, upgrade before you go looking for #5 — the conditions are subtle.
- Still on Next.js 14 or older? This release only ships patched builds for the 16.x and 15.x lines — plan the migration.