Technical impact
Next.js applications that enable Cache Components suffer from a concurrency flaw (CWE-362) that creates a race condition. When a nested use cache call reads a root parameter through next/root-params and returns a value containing pending promises, the outer cache may finish and persist the entry before the inner cache publishes its root‑param dependencies. Because the outer entry is stored under a key that omits the root parameter, the first value written will subsequently be served for all other root parameter values, leaking data that is not attacker‑controlled but depends on invocation order.
Affected Systems
Vulnerable releases include Next.js versions 16.2.0 through 16.4.5 from vercel:next.js. Any server‑side rendered application that uses Cache Components and employs next/root-params within nested use cache calls is affected, independent of the hosting environment.
Risk and Exploitability
The CVSS score of 6.3 indicates medium severity. EPSS is not available, and the vulnerability is not listed in CISA’s KEV catalog, suggesting no widespread exploitation yet. The attack vector is not explicitly defined in the advisory but involves shared cache state that could be influenced through crafted requests or timing attacks. Although the data leaked is not attacker‑controlled, cross‑context contamination can impact confidentiality, maintaining a moderate risk for sensitive applications.