What happened#
Next.js had announced a coordinated security release for 3 November, and it went out that day. The v16.4.5 release page (published 3 November, by a Next.js maintainer) says it “contains security fixes” for seven advisories, all Moderate. The v15.5.29 release page lists only three of them: the response injection, the SVG bypass and the Edge cookie exposure. That fits the advisories being about the 16.x-only use cache feature for the other four.
If you read last month’s post, Next.js security update, October 2026, that was the critical image-optimization and next/og release. This is a separate, lower-severity batch.
The seven advisories#
All seven are rated Moderate. Scores below are the CVSS 4.0 base scores shown on the advisory pages I read; where I could not read a field, the table says so.
| Issue | ID | Affects | Score |
|---|---|---|---|
| HttpOnly cookie exposed through an internal response header on Edge runtime routes | CVE-2026-119346 | 16.0.0 to 16.4.2 and 15.0.0 to 15.5.28 | 6.0 |
| SVG rejection bypass in image optimization | CVE-2026-119347 | 16.0.0 to 16.4.2 and 15.0.0 to 15.5.28 (self-hosted) | 6.9 |
| Cross-client response injection and disclosure in self-hosted apps forwarding fetched responses | CVE-2026-119348 | Range unclear on the page I read | 6.3 |
| Cross-user cache disclosure and poisoning in use cache with binary arguments | CVE-2026-119349 | 16.0.0 to 16.4.2 | 6.3 |
| Cache poisoning of shared fallback shells in Cache Components | CVE-2026-119350 | 16.4.0 and later; no patched version shown | 6.3 |
| Cache leak across root param values in nested use cache functions (follow-up) | CVE-2026-119351 | 16.2.0 and later | 6.3 |
| Information disclosure across root params when a use cache function is called through unstable_cache() | CVE-2026-119790 | 16.3.0 and later | 6.3 |
In plain terms, per the advisories:
- Edge cookies. If you set a cookie with
NextResponseon an Edge runtime route (an App Router route handler or a Pages Router Edge API route), the public response also carries an internalx-middleware-set-cookieheader that repeats the cookie’s value and attributes. The advisory says JavaScript on the same origin can then read cookies that were marked HttpOnly, such as a session token. Its score vector rates the attack complexity High and the user interaction Passive. - SVG bypass. On self-hosted deployments,
/_next/imagecan process an attacker-supplied SVG even withdangerouslyAllowSVGleft at its default offalse. The advisory describes the impact as increased exposure to denial of service and SVG decoder bugs, with only a low availability impact in its score. - Response injection. Self-hosted apps that return a fetched upstream response unchanged (from an App Router route handler or the fetch cache) can send a response whose declared framing doesn’t match its body. Behind an HTTP/1.1 reverse proxy that queues pipelined responses, the advisory says a crafted upstream response could desynchronize responses between clients. It rates the attack complexity High.
- Binary arguments to use cache. Functions marked
use cachethat take binary arguments such asUint8ArrayorBlobcan produce the same cache key for different arguments, so cached results can be shared across users. - Fallback-shell poisoning. Self-hosted apps running
next startwithcacheComponents: trueand Partial Prefetching off, with a dynamic route that has a blocking fallback shell and at least two never-prerenderable params. An unauthenticated GET request can poison a shared shell entry. The advisory says the effect is a cached 404 or an attacker-chosen value in the server-rendered HTML, and reports no injection or data disclosure. - Nested use cache and root params. Two related advisories: an inner cached function that reads a root param (for example a locale) can cause the outer entry to be cached under a key that leaves that param out, so one value’s content is served for another. The other covers a race when the same function is also called through
unstable_cache().
Am I affected?#
| If your app… | Look at |
|---|---|
| Uses use cache or Cache Components on Next.js 16 | Binary arguments to cached functions; nested use cache functions that read root params; use cache inside unstable_cache() |
| Sets cookies in Edge runtime routes | Route handlers or Pages API routes with runtime = “edge” that call NextResponse cookie methods |
| Self-hosts with next start | The image optimizer’s SVG handling, route handlers that return a fetched response unchanged, and cacheComponents with blocking fallback shells |
| Is on 16.x below 16.4.5 or 15.x below 15.5.29 | Upgrade is the fix either way; the patterns above tell you how urgent it is |
One honest caveat on versions. The advisory pages I read list some affected ranges that end at 16.4.2, while the release that carries the fixes is 16.4.5, and the follow-up root-param advisory’s page said “fixed in 16.4.2” even though the 16.4.5 notes list it. I could not reconcile that from the pages I could load, so I would not rely on a range to decide you are safe on 16.4.3 or 16.4.4. Upgrading to 16.4.5 is the unambiguous action.
What to do now#
- Upgrade to
16.4.5on 16.x or15.5.29on 15.x, and redeploy. - If you can’t upgrade today, the advisories list two workarounds: avoid nesting
use cacheinsideunstable_cache()(described as a complete workaround for that one), and setpartialPrefetching: trueinnext.configfor the fallback-shell issue. - Review Edge cookie routes. If a sensitive cookie is set on an Edge route, treat upgrading as the priority and consider whether that cookie could have been read by script on your origin.
- Check your own code for the patterns in the table above. A Next.js upgrade does not remove a design that leans on cache keys or HttpOnly cookies you have not looked at.
# Which Next.js is installed?
npm ls next
# Do you use the affected features?
grep -rn "use cache" app lib components 2>/dev/null
grep -rn "unstable_cache" app lib 2>/dev/null
grep -rn "runtime.*edge" app 2>/dev/null
grep -rn "cacheComponents\|partialPrefetching\|dangerouslyAllowSVG" next.config.* 2>/dev/null
# Upgrade within your major line, then rebuild and deploy
npm install next@16.4.5 # or next@15.5.29 on 15.xHow I checked this site#
This portfolio is a Next.js site on Vercel, and its package.json pins next at 16.4.3, so it is not on 16.4.5 yet. Searching its source, I found no use cache or unstable_cache, no cacheComponents or dangerouslyAllowSVG setting in next.config.ts, no middleware or proxy file, and no NextResponse or Edge runtime route. It uses next/image in a couple of components and has two route handlers (the RSS feed and the contact form). That means the patterns above do not appear in this site’s code. I have not read anything from my host about how these issues apply to its platform, so I am planning the upgrade rather than assuming I am safe.
What the sources don’t say#
- Whether anyone has exploited any of the seven. The pages I read don’t say.
- Exact patched versions for some advisories: several pages I could load showed none, and one range was internally unclear, as noted above.
- How a managed host treats the self-hosted-only issues. I did not read a hosting provider’s statement for this post.
- Severity labels differ between secondary write-ups in places; the release notes and the advisory pages I read rate all seven Moderate.
My take#
My own opinion, not from the advisories.
None of these is an emergency by its own rating, but they cluster around the newer caching model, where a missing key is easy to ship and hard to see in review. If you use use cache with anything user-specific, it is worth a read of your cache keys at the same time as the version bump. A secondary data point: one public project’s upgrade ticket, which I read, shows the same advisories being triaged in the same way, with the upgrade treated as routine because none of them tripped an audit gate set at high severity. That is a reminder that “Moderate” items are easy to defer, and a cookie or cache leak is a reason not to.
Sources#
- Next.js on GitHub: release v16.4.5 and release v15.5.29, primary sources
- Next.js security advisories: vercel/next.js advisories (individual pages linked in the table above), primary sources
- Third-party project upgrade ticket: Upgrade Next.js to 16.4.5 (project-forge issue 10438), a secondary account of the same advisories
Keep reading
8 min read
Next.js security update, October 2026: what to patch and how to check
Next.js 16.4.1 and 15.5.28 fix two critical remote code execution flaws and a denial-of-service bug. What each one needs to be exploitable, and how to check your app.
6 min read
@sentry/nextjs tunnelRoute bypass (CVE-2026-114139): can your Next.js middleware be skipped?
CVE-2026-114139 (CVSS 9.1) can let requests skip Next.js middleware when @sentry/nextjs tunnelRoute is set on a webpack build. Who is affected, and the fix.