Skip to main content
VulnerabilityPublished Updated

CVE-2026-94544: 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 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.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 16.3.8
CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:N/VA:N/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 vercel/next.js to 16.3.8.

Affected software

ProductAffectedFixed in
vercelnext.jsAffected
  • >=16.3.0 <16.3.8
Fixed in
  • 16.3.8
GitHubvercel/next.jspkg:github/vercel/next.jsOther threatsAffected
  • >=16.3.0 <16.3.8
Fixed in
  • 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

If you cannot patch yet, consider disabling Cache Components or the `experimental.useCache` feature if using Draft Mode previews to avoid cache contamination between draft and regular requests.

Description

CVE-2026-94544 is a medium severity vulnerability in Vercel's Next.js framework affecting versions >=16.3.0 and <16.3.8. It involves the use of a shared cache for pending `use cache` fills that does not distinguish between Draft Mode and regular requests. This can cause unpublished draft content to be served to unauthenticated users or published content to be served in draft previews. Additionally, if a regular request prerenders a page during this overlap, unpublished content may be persisted and served to all visitors until the page is revalidated.

References

Community reviews

Loading reviews…