Answer in brief
CVE-2026-119350 records a Medium severity (CVSS 6.3) vulnerability in Next.js: Cache poisoning of shared fallback shells in Cache Components via request-supplied placeholder route params. The current sources do not mark it as known exploited. The current feed maps vercel/next.js (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps vercel/next.js (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| vercel/next.jsgeneric | >=16.4.0 <16.4.5 | 16.4.5 |
Published upstream
Nov 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 16, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 16, 2026
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.
Quoted source text, attributed separately from HOL analysis.