
Must read
π Next.js November security release: seven advisories, patch now
Next.js 16.4.5 and 15.5.29 fix seven advisories. The high-severity one lets unstable_cache and use cache leak cached content across tenants when a root parameter (like a tenant ID) is read. Other fixes cover nested use cache leaking across root params, binary use cache args colliding, self-hosted shell cache poisoning, response mix-ups behind HTTP/1.1 proxies, cookie values exposed in an x-middleware-set-cookie header on Edge routes, and an SVG check bypass in image optimization.
Why it matters: Most bugs hit Cache Components, so any multi-tenant or per-locale app using use cache is exposed. Edge cookie leak affects even HttpOnly cookies if you have same-origin XSS.
Takeaway: Run npm install next@16.4.5 (or next@15.5.29) and check where you combine unstable_cache with use cache.
Read it fully? Yes, skim the severity notes for your setup (self-hosted, Edge, Cache Components).




