Next.js November 2026 Security Fixes: Check Your App
Résumé
Pixel shares details of the Next.js November 2026 security release, which fixes seven issues in versions 16.4.5 and 15.5.29. The announcement highlights cache leaks and poisoning risks, explains how to check installed versions, and recommends upgrading, redeploying, and clearing affected caches.
DEV Community
Next.js November 2026 security release: are you affected, and how to patch (16.4.5 and 15.5.29)
On 3 November 2026, the Next.js team released 16.4.5 and 15.5.29 to fix seven security issues. The most serious is a cache bug: in apps that use use cache, data cached for one tenant or locale can be served to another. Four of the seven involve Cache Components and only affect Next.js 16. That used to be a small group. Since Next.js 16.4, every new project made with create-next-app has Cache Components on by default, so it's now worth checking rather than assuming. The other three also affect Next.js 15. Short version: run npm ls next. If you're on 16.x below 16.4.5, or 15.x below 15.5.29, upgrade and redeploy. If your app uses use cache together with root parameters, also clear your caches after the upgrade, because wrong entries can outlive the fix. Last checked: 15 November 2026, against the Next.js blog post and the seven GitHub advisories. The seven issues at a glance Issue Advisory and CVE Affected versions You're exposed if Cache disclosure across root parameters when unstable_cache and use cache are combined GHSA-mfr8-8qww-v76h, CVE-2026-119790 16.3.0 to 16.4.4 The same use cache function is called both directly and from inside unstable_cache, and it reads a root parameter Cache leak across root parameters in nested use cache functions GHSA-vc7v-qv4w-wrv8, CVE-2026-119351 16.2.0 to 16.4.4 Cache Components is on, and one cached function calls another that reads a root parameter Cache disclosure and poisoning through binary use cache arguments GHSA-rhh4-g77r-r9qj, CVE-2026-119349 16.0.0 to 16.4.4 You pass binary values such as Uint8Array or Blob to a use cache function Shared shell cache poisoning GHSA-vvgp-ww4w-46vf, CVE-2026-119350 16.4.0 to 16.4.4 Self-hosted with next start, cacheComponents: true, Partial Prefetching off or unset Response mix-up when forwarding fetched responses GHSA-pc58-hwjq-p385, CVE-2026-119348 16.0.0 to 16.4.4, and 15.x up to 15.5.28 Self-hosted behind an HTTP/1.1 reverse proxy that pipelines requests, and your app returns a fetched Response unchanged HttpOnly cookie values exposed on Edge routes GHSA-f3mh-rxg3-f5g2, CVE-2026-119346 16.0.0 to 16.4.4, and 15.0.0 to 15.5.28 An Edge Route Handler or Edge API route sets a cookie through NextResponse SVG rejection bypass in Image Optimization GHSA-7qx7-33qx-rqx2, CVE-2026-119347 16.0.0 to 16.4.4, and 15.0.0 to 15.5.28 Self-hosted, and the image optimizer can be given an attacker-supplied image A note on severity. The Next.js blog post labels the first issue "High Severity" and the other six medium. On GitHub, all seven advisories are rated Moderate, with CVSS scores between 6.0 and 6.9. Either way, none is a remote code execution bug like the two in the October release. What each one means in plain words Cached data served to the wrong tenant or locale A root parameter is a dynamic segment that sits before the root layout, for example the [tenant] in app/[tenant]/layout.tsx or the [lang] in app/[lang]/layout.tsx. Code reads it with next/root-params. Apps use it to decide whose data, or which language, a page shows. Three of the cache bugs break that separation: unstable_cache plus use cache. Just after a server process starts, an unstable_cache call can pick up the result of another request's use cache call that is still in flight. It then stores that result under a key that ignores the root parameter. From then on, requests for other tenants or locales get the same entry until it's revalidated or evicted. Nested use cache functions. An outer cached function can be stored under a key that leaves out the root parameter its inner function read. The advisory adds that entries written this way can ignore tag invalidation and cache lifetimes. Binary arguments. Two different Uint8Array or Blob arguments can produce the same cache key, so one user can get another's cached result. In all three, an attacker can't choose what leaks. Which data gets served depends on which request filled the cache first. Shared shell poisoning (self-hosted) On a self-hosted...

Powered by Readybot.io