Interpretation Conflict Affecting next package, versions >=14.2.0-canary.0 <15.5.16>=16.0.0-beta.0 <16.2.5
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-16638676
- published11 May 2026
- disclosed11 May 2026
- creditUnknown
Introduced: 11 May 2026
NewCVE-2026-44576 (opens in a new tab)How to fix?
Upgrade next to version 15.5.16, 16.2.5 or higher.
Overview
next is a react framework.
Affected versions of this package are vulnerable to Interpretation Conflict via improper handling of shared cache entries for React Server Component responses. An attacker can cause unintended component payloads to be served to other users by manipulating shared cache behavior through crafted requests.
Workaround
This vulnerability can be mitigated by ensuring your CDN or reverse proxy keys on the relevant RSC request headers honor Vary, or by disabling shared caching for affected App Router and RSC responses.