CVE-2026-119350

Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params

Published Nov 16, 2026 CVSS 4.0 · 6.3 Medium EPSS n/a KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

From version 16.4.0 to 16.4.5, a self-hosted Next.js application using next start can accidentally store an attacker-supplied placeholder route parameter in a shared fallback shell when cacheComponents is enabled and partialPrefetching is disabled. The placeholder is incorrectly treated as unresolved, while the concrete value of the preceding route parameter is rendered into the shell and its HTTP status is cached. As a result, later requests that reuse the same shell may receive a misleading 404 status or a param value chosen by an attacker. No markup, script injection, or data disclosure is possible, and correct client‑side hydration restores the intended content. The primary effect is an indirect denial or falsification of content rather than direct code execution.

Affected Systems

The vulnerability exists in vercel:next.js versions 16.4.0 through 16.4.5, specifically for self-hosted deployments that render pages with cacheComponents enabled and do not use partialPrefetching. Applications must have a dynamic route that declares at least one prerenderable parameter via generateStaticParams that was not produced at build time, a nested route structure with two higher‑level never‑prerenderable parameters, a layout that reads the shallower parameter inside a Suspense boundary, and a blocking fallback shell.

Risk and Exploitability

The CVSS score of 6.3 indicates a medium severity. The EPSS score is unavailable, and the vulnerability is not listed in the CISA KEV catalog, suggesting a moderate likelihood of exploitation in the wild. An unauthenticated attacker can trigger the flaw by sending an HTTP request containing a placeholder route parameter that matches the percent‑encoded bracketed name of a deeper route parameter. Successful exploitation requires the specific route layout described above, so the attack window is limited to applications that meet those structural conditions.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Next.js to version 16.4.5 or later
  • Disable cacheComponents for dynamic routes that use fallback shells or restructure routes to avoid the vulnerable pattern
  • Implement monitoring for repeated 404 responses on affected routes to detect potential cache poisoning

Generated by OpenCVE AI on November 16, 2026 at 19:51 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Vercel
Vercel next.js
Vendors & Products Vercel
Vercel next.js
Type Values Removed Values Added
Description 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.
Title Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params
Weaknesses CWE-349
References
Metrics cvssV4_0

{'score': 6.3, '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'}

Weaknesses
  • CWE-349

    Acceptance of Extraneous Untrusted Data With Trusted Data

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Nov 16, 2026, 6:57 PM
Reserved
Oct 29, 2026, 8:44 PM
Status
Awaiting Analysis
Published
Nov 16, 2026, 7:17 PM
Modified
Nov 16, 2026, 8:37 PM