CVE-2026-94544: Next.js Vulnerability Allows Draft Mode Content Leakage
Summary
CVE-2026-94544: Pending use cache fills are shared across requests for the same key without distinguishing Draft Mode requests from regular requests. Affects next versions >= 16.3.0, < 16.3.8. Fixed in 16.3.8. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
Next.js is a popular React framework that enables developers to build server-rendered applications with ease. It offers features like static site generation, server-side rendering, and API routes. However, a vulnerability has been identified in versions prior to 16.3.8, where pending use cache fills can inadvertently expose Draft Mode content to unauthorized users.
Vulnerability Detail
The vulnerability arises from the way Next.js handles cache fills for Draft Mode requests. When a Draft Mode request overlaps with a regular request, the second request can receive the first request's fill. This means that a regular request can access unpublished content without authentication, while a Draft Mode request may receive published content instead of the draft. If a regular request prerenders a page, the unpublished content can be persisted and served to all subsequent visitors until the page is revalidated. This poses a significant risk to sites that enable Cache Components and serve Draft Mode previews.
How To Fix
Latest published version: 16.4.2 as of 22 Oct 2026
npm install next@16.4.2Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.
If you need the minimum change
16.3.8
This is the first release that contains the fix.
npm install next@16.3.8Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, consider disabling the Cache Components feature or avoiding the use of Draft Mode until you can update to the patched version. This will help mitigate the risk of content leakage.
Conclusion
The identified vulnerability in Next.js (CVE-2026-94544) poses a risk of leaking Draft Mode content through improper cache handling. It is crucial to update to version 16.3.8 or later to mitigate this risk. Additionally, utilizing tools like Vulert can help in monitoring and managing vulnerabilities effectively.
See every vulnerability recorded for next →
FAQ
The CVSS score of this vulnerability is 4.2, indicating a moderate severity level.
Next.js versions prior to 16.3.8 are affected by this vulnerability.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
The vulnerability can lead to unauthorized access to unpublished content, which may compromise the integrity and confidentiality of your application.
Yes, Vulert can monitor your project for open-source vulnerabilities in real-time using just the package-lock.json file.
References
Related vulnerabilities
Recent vulnerabilities recorded for next.
