Skip to main content
VulnerabilityPublished Updated

CVE-2026-94484: vercel next.js · Use of Cache Containing Sensitive Information

Affects vercel next.jsSource CVE Database V5

0
Compare

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

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 15% 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:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
vercelnext.jsAffected
  • >=16.0.0 <16.3.8
Fixed in
  • 16.3.8
vercelnext.jsAffected
  • >=15.0.0 <15.5.27
Fixed in
  • 15.5.27
npmnextpkg:npm/nextOther threatsAffected
  • >=15.0.0 <15.5.27
  • >=16.0.0 <16.3.8
Fixed in
  • 15.5.27
  • 16.3.8

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 to version 16.3.8 or later in the 16.x series, where this vulnerability is fixed. No other mitigation is indicated by the vendor advisory.

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 a shared response cache key is insufficiently scoped. This allows an unauthenticated attacker to poison the cache via a crafted request, potentially causing cross-user content substitution or persistent denial of service until the cache entry is refreshed. The issue is fixed in versions 15.5.27 and 16.3.8.

References

Community reviews

Loading reviews…