CVE-2026-119350: Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params
Next.js is a React framework for building full-stack web applications. From 16.4.0 until 16.4.5, self-hosted Next.js applications served with next start can allow an unauthenticated request to poison a shared fallback shell when cacheComponents is true and partialPrefetching is unset or false. The affected dynamic route must have a prerenderable param declared by generateStaticParams whose requested value was not generated at build time, at least two never-prerenderable params below it, a layout that reads the shallower param inside a Suspense boundary, and a blocking fallback shell. A request-supplied placeholder route param whose path segment equals the percent-encoded bracketed name of its own deeper route param is incorrectly treated as unresolved, while the shallower concrete value is rendered into the shared shell and its HTTP status is persisted. Depending on application behavior, subsequent routes sharing that shell can receive a persistent 404 or attacker-selected substituted param text. Client hydration corrects substituted text, and the issue does not enable markup or script injection or disclose data. This issue is fixed in version 16.4.5.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Next.jsto a version that resolves this vulnerability.Fixed in 16.4.5
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
The issue affects self-hosted applications served with next start on Next.js versions 16.4.0 through 16.4.5 when cacheComponents is enabled and partialPrefetching is unset or false. It also requires a dynamic route with the specific generateStaticParams, nested never-prerenderable parameter, Suspense layout, and blocking fallback-shell conditions described.
What must an attacker do to trigger the cache poisoning?
An unauthenticated attacker must request an affected route using a placeholder route parameter whose path segment equals the percent-encoded bracketed name of its own deeper route parameter. The shallower parameter value can then be rendered into and persisted in the shared fallback shell, potentially causing later requests sharing that shell to receive a persistent 404 or substituted text.
Is there a risk of script injection or data disclosure?
No. The issue does not enable markup or script injection and does not disclose data; client hydration corrects substituted text.
What remediation is available?
Upgrade Next.js to version 16.4.5, which contains the fix. The provided data does not specify a workaround for deployments that cannot be upgraded immediately.