MediumGHSA-vvgp-ww4w-46vfCVE-2026-119350

Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params

Published 19 Nov 2026 · Updated 19 Nov 2026

Is your project on an affected next?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several JavaScript apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Affected package

nextnpm
Affected
>=16.4.0 <16.4.5
Fixed in
16.4.5
Update to the fixed version for your release line, for example:npm install next@16.4.5

Details

Self-hosted Next.js applications served with next start and built with cacheComponents: true but without Partial Prefetching accept a request-supplied route param value as a prerender placeholder. One unauthenticated GET request can poison the fallback shell cache entry that a family of routes shares.

Such a route is served from a shell that keeps its never-prerenderable params as placeholders, so every value of those params shares one cache entry. A path segment equal to the percent-encoded, bracketed name of its own route param is treated as an unresolved placeholder, and only that param is deferred. A layout above it then renders its concrete value into the shell during the blocking render, and the result, including its HTTP status, is stored under the shared key.

Depending on the application, the stored entry is one of the following:

  • A persistent 404, when the layout rejects the value with notFound(): served to every URL under the shell key with "revalidate": false, across server restarts, with no error logged.
  • A substituted param value, when the layout renders the value: the server-rendered HTML renders the attacker's value for that param in place of the visitor's own. A JavaScript client corrects it on hydration. No markup or script injection is possible, and no data is disclosed.

Preconditions

1. cacheComponents: true with partialPrefetching unset or false. 2. Self-hosted serving with next start. 3. A dynamic route with a prerenderable param (generateStaticParams) whose requested value was not generated at build time. 4. At least two never-prerenderable params below it: a layout reading the shallower one inside a Suspense boundary, and a deeper one the request supplies as the placeholder. 5. A blocking fallback shell.

Workarounds

Set partialPrefetching: true in next.config. Otherwise, apps should upgrade to the patched version as soon as possible.

Is GHSA-vvgp-ww4w-46vf in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected next, and gives you the command that fixes it.

More advisories for next

  • MediumCVE-2026-119346Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes · 19 Nov 2026
  • MediumCVE-2026-119347Next.js: SVG rejection bypass in the image optimization · 19 Nov 2026
  • MediumCVE-2026-119348Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses · 19 Nov 2026
  • MediumCVE-2026-119349Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments · 19 Nov 2026
  • MediumCVE-2026-119351Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata · 17 Nov 2026
  • MediumCVE-2026-119790Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache() · 16 Nov 2026
All 84 advisories for next

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.