CVE-2026-119350: Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params
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.
Published Nov 19, 2026
Affected packages
next
- Ecosystem
- npm
- Affected
- >= 16.4.0, <= 16.4.4
- Fixed in
- 16.4.5
- Check
npm ls next
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
cacheComponents: truewithpartialPrefetchingunset orfalse.- Self-hosted serving with
next start. - A dynamic route with a prerenderable param (
generateStaticParams) whose requested value was not generated at build time. - 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.
- A blocking fallback shell.
Workarounds
Set partialPrefetching: true in next.config. Otherwise, apps should upgrade to the patched version as soon as possible.
References
- https://github.com/vercel/next.js/security/advisories/GHSA-vvgp-ww4w-46vf
- https://nvd.nist.gov/vuln/detail/CVE-2026-119350
- https://github.com/vercel/next.js/commit/18eeffb5fabd91911852d44cf56948b3f2cbee04
- https://github.com/vercel/next.js/releases/tag/v16.4.5
- https://nextjs.org/blog/november-2026-security-release
- https://github.com/advisories/GHSA-vvgp-ww4w-46vf
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-119346
Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routes
medium6.0Nov 19, 2026CVE-2026-119347
Next.js: SVG rejection bypass in the image optimization
medium6.9Nov 19, 2026CVE-2026-119348
Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responses
medium6.3Nov 19, 2026CVE-2026-119349
Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary arguments
medium6.3Nov 19, 2026CVE-2026-119351
Next.js: Cache leak across root param values in nested 'use cache' functions via delayed inner stream metadata
medium6.3Nov 17, 2026CVE-2026-119790
Next.js: Information disclosure across root params when a 'use cache' function is called through unstable_cache()
medium6.3Nov 16, 2026
