Use of Cache Containing Sensitive Information Affecting next package, versions >=16.3.0 <16.3.8
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-NEXT-20569638
- published8 Oct 2026
- disclosed1 Oct 2026
- creditUnknown
Introduced: 1 Oct 2026
NewCVE-2026-103004 (opens in a new tab)How to fix?
Upgrade next to version 16.3.8 or higher.
Overview
next is a react framework.
Affected versions of this package are vulnerable to Use of Cache Containing Sensitive Information via incorrect cache keying in nested 'use cache' function handlers that access root params. When Cache Components is enabled (cacheComponents: true), a 'use cache' function that calls another 'use cache' function which reads a root param can be keyed incorrectly when the inner call is served from an existing cache entry: the enclosing function's cache key then omits that root param. The enclosing entry is written once and reused for all root param values, so a response for one root param value can serve content produced for a different value, whether the page is prerendered at build time, at runtime, or rendered dynamically, and shared cache headers allow downstream caches to redistribute the mismatched content further.
Note: This is only exploitable when the cacheComponents: true option is enabled and the application uses nested 'use cache' functions where the inner function reads a root param.