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.