CVE-2026-75604: React2Shell2: Windows incremental-cache path traversal in Next.js
CVE-2026-75604 is a Windows-specific path traversal vulnerability in Next.js incremental-cache handling. It affects versions 13.4.0 through 15.5.23 and 16.0.0 through 16.3.2 in qualifying Pages Router and App Router deployments without Cache Components. Inconsistent escaping of backslashes in route segments allows remotely supplied encoded Windows path separators to escape the intended filesystem cache root. Exploitation can disclose files accessible to the application process, including private build data and the Server Actions encryption key, and can write cache-rendered content outside the intended cache directory. A disclosed encryption key permits forgery of encrypted Server Action arguments and, with susceptible application patterns and framework versions, unauthenticated remote code execution. Linux and macOS deployments are not affected.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation compromises confidentiality through disclosure of application source, build metadata, encryption keys, and other files readable by the Next.js process. The write primitive can place cache-rendered responses at attacker-selected locations, subject to fixed extensions, templated content, and filesystem permissions, potentially modifying application data or disrupting availability. Exposure of the Server Actions encryption key can enable authorization bypass through forged closure-bound values. Under additional version and application prerequisites, this can escalate to arbitrary code execution with the privileges of the Node.js process; administrative or SYSTEM privileges are not inherent to exploitation.
Mitigation
If you can’t patch tonight, do this now.
No vendor-supported in-place configuration workaround is known for affected Windows deployments. Until patched, restrict access from untrusted networks. As a supplementary control, configure a WAF or reverse proxy to reject literal backslashes and single- or double-percent-encoded backslashes in request paths, evaluating both raw paths and paths after decoding; test for legitimate traffic impact and do not treat filtering as equivalent to patching. Moving the runtime to Linux or macOS removes the Windows-specific traversal condition but does not invalidate previously stolen keys. A custom cache handler that avoids the vulnerable filesystem path requires application-specific validation and should not be assumed to provide protection.
Remediation
Patch, then assume compromise.
Upgrade and redeploy affected applications to Next.js 15.5.24 or later patched releases in the 15.x line, or 16.3.3 or later patched releases in the 16.x line. Applications on affected 13.x and 14.x releases must migrate to a patched release line. Verify the versions running in all production and nonproduction Windows deployments. Treat potentially exposed Server Actions encryption keys as compromised and rotate them after deploying the fix. A routine rebuild or upgrade may preserve the previous key through build caches or an explicitly pinned build-time key. Clear relevant cached key material before rebuilding, or replace the pinned build-time key, and redeploy consistently to every environment sharing that key. If exploitation is suspected or confirmed, rotate other secrets accessible to the application process.
Exploits
4 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.
References
Frequently asked questions
- Is CVE-2026-75604 exploited in the wild?
- Yes. As of Nov 9, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2026-75604?
- Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2026-75604, the earliest disclosed Aug 25, 2026.
- Is there a patch for CVE-2026-75604?
- Upgrade and redeploy affected applications to Next.js 15.5.24 or later patched releases in the 15.x line, or 16.3.3 or later patched releases in the 16.x line. Applications on affected 13.x and 14.x releases must migrate to a patched release line.
- How severe is CVE-2026-75604?
- CVE-2026-75604 has a CVSS v3.1 score of 9.0 (Critical) and an EPSS score of 2.1% (82nd percentile) as of Nov 9, 2026.
Recent activity
59 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.