CVE-2026-94484
next: Next.js: Denial of Service via response cache poisoning
Severity
ModerateRed Hat Product Security
CVSS 3.1
Review impact separately from score.
Published · October 3, 2026
Updated · October 30, 2026
Description
A flaw was found in Next.js. Applications configured with root-level catch-all pages and static routes share a response cache key that does not properly distinguish between different routes. A remote, unauthenticated attacker can exploit this vulnerability by sending a specially crafted request to poison the shared application cache. Successful exploitation can result in a persistent Denial of Service (DoS) or cause unauthorized content substitution across different users until the cache entry is refreshed.
Statement
This vulnerability is rated as having a Moderate impact for Red Hat products because, although exploitation can be triggered remotely without authentication, it requires a specific application routing architecture combining root catch-all handlers with statically generated pages. While successful cache poisoning can disrupt service availability or serve incorrect responses to subsequent clients, it does not allow remote code execution or direct data compromise. Red Hat environments utilizing Next.js are only susceptible if the deployed web frontend actively implements Incremental Static Regeneration alongside root catch-all route definitions.
CVSS score applicability
The CVSS score(s) listed for this vulnerability do not reflect the associated product's status, and are included for informational purposes to better understand the severity of this vulnerability.
Mitigation
No mitigation is specified in collected source.
CVSS / CWE
CVSS 3.1 · 6.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L
CWE-694 · Use of Multiple Resources with Duplicate Identifier