CVE-2026-94543: vercel next.js · Use of Cache Containing Sensitive Information
Affects vercel next.jsSource CVE Database V5
Not known to be exploited · CVSS 6.3 Medium : upgrade to 16.3.8 or 15.5.27 when convenient.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 43% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 16.3.8, 15.5.27
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 2 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade next.js and next to 16.3.8 or 15.5.27.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| vercelnext.js | Affected
| Fixed in
|
| vercelnext.js | Affected
| Fixed in
|
npmnextpkg:npm/nextOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Next.js to version 15.5.27 or later in the 15.x series, or 16.3.8 or later in the 16.x series to apply the official fix. Applications deployed on Vercel are not affected and require no action. For self-hosted deployments, applying these updates will resolve the issue.
Description
Next.js versions from 15.0.0 up to but not including 15.5.27, and from 16.0.0 up to but not including 16.3.8, contain a vulnerability where the response cache for statically generated or Incremental Static Regeneration pages using the Pages Router can be incorrectly keyed. This allows a request to replace one page's cached content with that of another route, causing incorrect content to be served to visitors until the cache is revalidated. Applications deployed on Vercel are not affected. The issue is fixed in versions 15.5.27 and 16.3.8.
References
- github.com/vercel/next.js/security/advisories/GHSA-4jqv-mc3x-m676 (opens in a new tab)
- github.com/vercel/next.js/commit/52c94abdd2ea5f416f5e8353ea8a2edd3fe311b8 (opens in a new tab)
- github.com/vercel/next.js/commit/719e4c67d6e92df60246f95e1d96e2dd60789a52 (opens in a new tab)
- github.com/vercel/next.js/releases/tag/v15.5.27 (opens in a new tab)
- github.com/vercel/next.js/releases/tag/v16.3.8 (opens in a new tab)