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.
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.
Affected software
Click a technology to see all vulnerabilities affecting it.
| Platform | Package | Vulnerable versions | Fixed in |
|---|---|---|---|
| npm package | next | >= 16.4.0, < 16.4.5 | 16.4.5 |
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
- https://github.com/vercel/next.js/releases/tag/v16.4.5
- https://nextjs.org/blog/november-2026-security-release
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N- Weakness (CWE)
CWE-349- Platform
- npm
- Package
next- Disclosed
- 19.11.2026
- Updated
- 20.11.2026 00:17
Sources and licenses
OSV / GitHub Advisory Database - GHSA-vvgp-ww4w-46vf - CC BY 4.0
Vulnerability history: next
All published vulnerabilities of this package (npm package), newest first. Shows whether this is a one-off slip or a package that needs watching.
- Total entries
- 83
- First → latest
- 12.2017 11.2026
- Without a fix
- 0
- Exploited in attacks
- 0
Severity breakdown
- Critical 6
- High 28
- Medium 40
- Low 9
Disclosures per year
- 2017: 1
- 2018: 2
- 2019: 0
- 2020: 3
- 2021: 3
- 2022: 3
- 2023: 1
- 2024: 6
- 2025: 14
- 2026: 50
-
Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params this entry
Know which vulnerabilities affect your application
With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.