CVE-2026-119350
Received Received - Intake

Next.js Cache Poisoning via Unauthenticated Requests

Vulnerability report for CVE-2026-119350, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-16

Last updated on: 2026-11-16

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-16
Last Modified
2026-11-16
Generated
2026-11-16
AI Q&A
2026-11-16
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
vercel next.js to 16.4.5 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-349 The product, when processing trusted data, accepts any untrusted data that is also included with the trusted data, treating the untrusted data as if it were trusted.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability is a cache poisoning issue in Next.js applications using shared fallback shells with cacheComponents set to true. It occurs when request-supplied route parameters are incorrectly treated as prerender placeholders, allowing an unauthenticated attacker to manipulate cached responses. The attack requires specific conditions like dynamic routes with never-prerenderable parameters and a blocking fallback shell.

Detection Guidance

To detect this vulnerability, monitor Next.js applications running versions 16.4.0 to 16.4.4 with cacheComponents set to true and partialPrefetching unset or false. Check for unusual 404 errors or unexpected parameter substitutions in dynamic routes with specific prerequisites. Inspect server logs for requests with crafted path segments matching percent-encoded bracketed route parameter names.

Impact Analysis

The impact includes persistent 404 errors for users or substitution of attacker-controlled parameter values in rendered HTML. While it does not enable data disclosure or script injection, it can disrupt application behavior by serving incorrect responses. Client-side hydration may correct substituted text, but the issue affects route integrity and availability.

Mitigation Strategies

Upgrade Next.js to version 16.4.5 or later. Alternatively, enable partialPrefetching by setting it to true in your Next.js configuration. This addresses the root cause by preventing request-supplied placeholders from contaminating shared shell entries.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-119350. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...