Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params
GHSA-vvgp-ww4w-46vf · CVE-2026-119350
Published · Modified
AI SAST
Find this class of vulnerability in your own code
Corgea's AI-native static analysis detects vulnerabilities like this one across your repositories, ranks them by exploitability, and returns review-ready fixes.
Description
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
- WEB https://github.com/vercel/next.js/security/advisories/GHSA-vvgp-ww4w-46vf
- ADVISORY https://nvd.nist.gov/vuln/detail/CVE-2026-119350
- WEB https://github.com/vercel/next.js/commit/18eeffb5fabd91911852d44cf56948b3f2cbee04
- PACKAGE https://github.com/vercel/next.js
- WEB https://github.com/vercel/next.js/releases/tag/v16.4.5
- WEB https://nextjs.org/blog/november-2026-security-release
Ready to move
Start Securing
Free, no credit card | First findings in minutes