Summary
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.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-119350? CVE-2026-119350 is a medium-severity security vulnerability in next (npm), affecting versions >= 16.4.0, <= 16.4.4. It is fixed in 16.4.5.
- Which versions of next are affected by CVE-2026-119350? next (npm) versions >= 16.4.0, <= 16.4.4 is affected.
- Is there a fix for CVE-2026-119350? Yes. CVE-2026-119350 is fixed in 16.4.5. Upgrade to this version or later.
- Is CVE-2026-119350 exploitable, and should I be worried? Whether CVE-2026-119350 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-119350 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-119350? Upgrade
nextto 16.4.5 or later.