PT-2026-148424
CVE-2026-119350
·
Published
2026-11-16
·
Updated
2026-11-19
Description by
CVSS 4.0
6.3
MediumMetricsAV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Name of the Vulnerable Software and Affected Versions
Next.js versions 16.4.0 through 16.4.4
Description
Self-hosted applications served with
next start may allow an unauthenticated request to poison a shared fallback shell. This occurs when cacheComponents is true and partialPrefetching is unset or false. The issue requires a dynamic route with a prerenderable parameter declared by generateStaticParams that was not generated at build time, at least two never-prerenderable parameters below it, a layout reading the shallower parameter inside a Suspense boundary, and a blocking fallback shell. A request-supplied placeholder route parameter whose path segment equals the percent-encoded bracketed name of its own deeper route parameter is incorrectly treated as unresolved. Consequently, the shallower concrete value is rendered into the shared shell and its HTTP status is persisted, potentially causing subsequent routes sharing that shell to receive a persistent 404 or attacker-selected substituted parameter text. Client hydration corrects substituted text, and the issue does not allow markup or script injection or data disclosure.Recommendations
Update to version 16.4.5.
Found an issue in the description? Have something to add? Feel free to write us 👾