Quick answers
- Is CVE-2026-94544 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-94544 being exploited in the wild.
- How severe is CVE-2026-94544?
- Medium severity, with a CVSS score of 4.2, published 2 October 2026.
- Which products and versions are affected?
- next (npm) >= 16.3.0, < 16.3.8, SEMVER:introduced=16.3.0,fixed=16.3.8; Vercel Next.js 16.3.0 through 16.3.7.
- Is there a fix for CVE-2026-94544?
- Yes. next (npm): upgrade to 16.3.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-94544 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-94544?
- Check whether you run next (npm) or Vercel Next.js at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- next (npm): upgrade to 16.3.8 or later
npm install next@16.3.8
Technical details
The vulnerability occurs in the use cache deduplication mechanism, which shares pending cache fills for identical keys across concurrent requests without distinguishing Draft Mode requests from regular requests. An overlapping regular request can receive draft-dependent content, and if that request prerendered a page, the contaminated content persists in the static output. The issue affects deployments with Cache Components or experimental.useCache enabled that return draft-dependent cached content.
Affected products
- Vercel Next.js 16.3.0 through 16.3.7
Identifiers
- CVE-2026-94544
- GHSA-3w37-wq28-93x7
Timeline
- 2026-10-02: disclosed