Technical impact
The flaw is a race condition that enables a malicious request to read cached data from another request that carries a different root parameter. During a cold start, the first use of a cached value can be co‑opted by a second concurrent call that reaches the unstable_cache() wrapper while the initial fill is still in flight. Because the cache key does not include the root param, the result is stored under a generic key and subsequent requests for other root param values retrieve the same data. The impact is the inadvertent exposure of sensitive cached information, potentially leaking data between unrelated users. This weakness falls under CWE‑362 Race Condition.
Affected Systems
Vercel’s Next.js framework versions 16.3.0 through 16.4.5 are affected. The vulnerability exists in the internal use of a 'use cache' function during rendering when accessed via unstable_cache(). No other front‑end or back‑end components are mentioned as vulnerable.
Risk and Exploitability
The risk is moderate because the vulnerability can be abused through concurrent HTTP requests, but it requires precise timing and does not provide arbitrary code execution. The CVSS score is 6.3, EPSS is not available, and the issue is not in KEV. Provided the application exposes sensitive cached data, the potential impact is the inadvertent leakage of that data to other users. The race can be triggered by a legitimate request from an attacker with sufficient control over the root parameter. If the application developer is unable to control the request timing, mitigating via code changes or upgrading to the fixed version is recommended.
Github GHSA