Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-94544 Overview
CVE-2026-94544 affects Next.js, the React framework from Vercel used to build full-stack web applications. The flaw exists in versions 16.3.0 through 16.3.7 when Cache Components or experimental.useCache is enabled. Pending 'use cache' fills for the same key are shared across requests without separating Draft Mode traffic from regular traffic. An overlapping regular request can receive unauthenticated unpublished editor content, and an overlapping Draft Mode request can receive published content from a regular fill. When a regular request prerenders a page, the draft-dependent content can persist in the generated page until revalidation. The issue is fixed in Next.js 16.3.8.
Critical Impact
Unpublished Draft Mode content can leak into prerendered pages served to unauthenticated visitors until the cache entry is revalidated.
Affected Products
- Vercel Next.js 16.3.0 through 16.3.7
- Deployments with Cache Components enabled
- Deployments with experimental.useCache enabled and cached functions returning draft-dependent content
Discovery Timeline
- 2026-10-02 - CVE-2026-94544 published to NVD
- 2026-10-05 - Last updated in NVD database
Technical Details for CVE-2026-94544
Vulnerability Analysis
The vulnerability is a cross-context cache deduplication flaw ([CWE-524]: Use of Cache Containing Sensitive Information). Next.js deduplicates concurrent 'use cache' fills so that multiple in-flight requests resolving to the same cache key share a single computation. The deduplication logic correctly isolates private responses but does not account for Draft Mode as a separate request context.
Draft Mode in Next.js lets editors preview unpublished content fetched from a CMS. When a Draft Mode request and a regular request race on the same cache key, whichever request initiates the fill supplies the response for the other. A regular visitor can therefore receive editor-only draft content, and an editor can receive stale published content instead of the draft they expected.
The higher-impact scenario occurs when the regular request is a prerender. The draft-dependent output is written into the generated page and persists in the shared cache, exposing unpublished content to subsequent unauthenticated visitors until revalidation.
Root Cause
In packages/next/src/server/use-cache/use-cache-wrapper.ts, the skipCrossRequestDedupe condition only considered the isPrivate flag. The workStore.isDraftMode state was not propagated into the dedupe key or the skip condition, so Draft Mode and regular fills with identical cache keys were treated as interchangeable.
Attack Vector
Exploitation requires a concurrent request pattern against a vulnerable Next.js application. An attacker, or a benign visitor, needs to issue a request that races against an editor's active Draft Mode session on a cached route. No authentication is required for the regular request that receives the leaked draft content. The attack complexity is elevated because the attacker must time requests to overlap with an active Draft Mode fill.
// Security patch in packages/next/src/server/use-cache/use-cache-wrapper.ts
// headers, so concurrent requests with identical request data should share
// a fill too; that request-scoped `cacheHandlerKey` keeps requests with
// different cookies or headers in separate entries.
- const skipCrossRequestDedupe = isPrivate && !process.env.__NEXT_DEV_SERVER
+ //
+ // Draft mode requests are skipped as well, in both directions. A fill that
+ // runs with draft mode enabled can contain unpublished content, so it must
+ // not be registered for other requests to join. And a draft mode request
+ // must not join a pending public fill, because it would be served the
+ // published content instead of the draft.
+ const skipCrossRequestDedupe =
+ (isPrivate && !process.env.__NEXT_DEV_SERVER) || workStore.isDraftMode
Source: vercel/next.js commit bd9214f
Detection Methods for CVE-2026-94544
Indicators of Compromise
- Unpublished CMS content appearing in cached pages served to unauthenticated users.
- Editors reporting that Draft Mode previews occasionally display published, non-draft content.
- Prerendered output in the .next/cache directory containing fields that only Draft Mode code paths populate.
Detection Strategies
- Audit the running Next.js version against 16.3.0 through 16.3.7 with Cache Components or experimental.useCache enabled.
- Review cached functions for branches that read draftMode() or produce content conditional on Draft Mode state.
- Compare rendered output between authenticated editor sessions and anonymous sessions for the same cached route.
Monitoring Recommendations
- Log Draft Mode cookie presence alongside cache hit and miss events for 'use cache' entries.
- Monitor CDN and edge caches for revalidation anomalies on routes used by editorial workflows.
- Alert on unexpected content diffs between successive prerenders of the same route.
How to Mitigate CVE-2026-94544
Immediate Actions Required
- Upgrade Next.js to version 16.3.8 or later across all environments.
- Trigger a full cache revalidation after upgrading to purge any poisoned prerendered pages.
- Audit cached functions and refactor any that mix draft and published content paths behind the same cache key.
Patch Information
Vercel fixed the issue in Next.js 16.3.8 by including workStore.isDraftMode in the skipCrossRequestDedupe condition and propagating the isDraftMode flag through the app route template. Review the GitHub Security Advisory GHSA-3w37-wq28-93x7 and the Next.js v16.3.8 release notes for complete patch details.
Workarounds
- Disable experimental.useCache and Cache Components until the upgrade is deployed.
- Restrict Draft Mode access to isolated preview deployments that do not share caches with production traffic.
- Avoid returning draft-dependent values from functions annotated with 'use cache'.
# Upgrade Next.js to the patched release
npm install next@16.3.8
# Verify the installed version
npx next --version
# Clear the build cache before redeploying
rm -rf .next
npm run build
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

