Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2026-75604: React2Shell2: Windows incremental-cache path traversal in Next.js

Published Sep 1, 2026 · Updated 9 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days1 mention · peak 1 in a dayToday
CVSS9.0Critical · v3.1
EPSS2.1%82nd percentile
CISA KEVNoNot listed
In the wildReported1 exploitation record in Mallory
IdentifiersCVE-2026-75604CWE-22 · Improper Limitation of a Pathname…

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

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.

View more in app →
CVE-2026-75604-pocThis is a standalone Python 3 proof-of-concept exploit, not a module from a recognized exploit framework. Its primary entry point, `poc.py`, targets CVE-2026-75604 in vulnerable Windows Next.js deployments. It validates an HTTP(S) target, obtains a Pages Router build ID, and uses Windows backslash-encoded traversal sequences (`..%5C`) through both App Router and Pages Router cache routes to retrieve the Next.js server-reference manifest. The manifest provides the Server Action encryption material/metadata needed to construct a malicious encrypted Server Action request. The PoC then invokes a compatible closure-bound Server Action to execute the configurable command and waits on an attacker callback listener for confirmation. It includes explicit vulnerable/not-vulnerable/inconclusive error handling, TLS-verification disablement, target and callback timeouts, and automated HTML form-field discovery when possible. The repository also contains an optional local reproduction target under `target/`. It is a small mixed-router Next.js application pinned to Next.js 16.2.11: `target/pages/pages-cache/[...rest].js` creates a dynamic ISR Pages route, `target/app/app-cache/[...rest]/page.js` creates a revalidated App Router route, and `target/app/page.js` defines the closure-bound Server Action used by the PoC. `target/package.json` builds and launches the demonstration server on port 4330. Python dependencies are limited to `requests` and `cryptography`, the latter supporting AES-GCM handling of Server Action data. No fixed third-party C2, public target IP address, registry persistence, or destructive behavior is present; target and callback addresses are supplied at runtime.rafabd1 · Disclosed Aug 25, 2026 · python · javascript · web · networkOperationalCVE-2026-75604This is a standalone Python 3 proof-of-concept exploit for CVE-2026-75604 / GHSA-p293-qw3h-jr36, rather than a Metasploit, Nuclei, or other framework module. The primary entry point, poc.py (about 15 KB), validates a target origin, discovers a Pages Router build ID, constructs encoded `..%5C` cache traversal requests, and retrieves the Next.js Server Action reference manifest. The intended Windows-specific flaw is improper handling of encoded backslash path delimiters by Next.js FileSystemCache. The manifest leak exposes the Server Action encryption key and action data needed to create a forged encrypted closure-bound Server Action invocation, resulting in arbitrary command execution. The PoC accepts a customizable command (default `whoami`) and runs an HTTP callback listener for execution output/confirmation. It includes error handling that distinguishes not-vulnerable and inconclusive cases, HTML form parsing to identify the compatible Server Action field, TLS-verification disabling via --insecure, and configurable timeouts/callback settings. The repository also includes a deliberately vulnerable local Next.js 16.2.11 target under target/: an App Router cached route, a Pages Router ISR route, and a root Server Action whose closure pattern satisfies the exploit precondition. requirements.txt identifies cryptography and requests dependencies; package.json/package-lock.json pin the demonstration application's Next.js and React dependencies.HackSpeak · Disclosed Aug 26, 2026 · python · javascript · networkOperationalProject-CVE-2026-75604This is a small standalone Python repository containing one executable exploit tool, NextRCE.py, plus a README, MIT license, and a standard Python .gitignore. It is not a Metasploit, Nuclei, or other recognized exploit-framework module. The script accepts a target URL, callback IP/port, cache type, payload type, optional HTTP(S) proxy, and a check-only flag. It first offers lightweight Next.js fingerprinting by requesting the target root page and the public /_next/static/chunks/main.js asset, checking for X-Powered-By: Next.js and __next markers. Its active path constructs POST requests to /pages-cache/seed or /app-cache/seed with several Windows backslash and percent-encoded dot-segment traversal patterns. It attempts to deliver JavaScript intended either to create a Node.js cmd.exe reverse shell or a command-executing Next.js API webshell; custom payload content and destination paths are also supported. The README describes the claimed target as CVE-2026-75604 affecting certain Windows-hosted Next.js cache configurations, and identifies 15.5.24 and 16.3.3 as fixed releases. The check-only feature is detection/fingerprinting functionality, but the repository also contains active payload-delivery and command-execution logic, so it is not solely a detection script. Functional exploitability cannot be established from the fingerprinting checks alone and depends on the claimed vulnerable cache implementation and deployment configuration.e4zyy · Disclosed Aug 27, 2026 · python · javascript · network · webOperationalcve-2026-75604This 26-file JavaScript/PowerShell research lab targets CVE-2026-75604 in Next.js incremental-cache path handling on Windows. The primary exploit, exploit.mjs, derives a public build ID, sends an App Router cache-warming request containing `..%5C`, and reads the same traversed cache key through a Pages Router `/_next/data/` endpoint. It explicitly documents that the disclosure is destructive: cache persistence subsequently overwrites the accessed target with route-generated content. `flight-forge.mjs` and `forge-cli.mjs` implement offline AES-GCM decryption/encryption of Server Action bound arguments using a stolen manifest key. `send-action.mjs` and rce-chain.mjs assemble a forged React Flight `constructor:constructor` gadget and a multipart Server Action request carrying Node/Windows command-execution JavaScript. The repository also includes a deliberately vulnerable minimal Next.js application, a Windows build/start script, reproduction instructions, evidence, and version research. Importantly, the included 16.3.2 app dependency remains traversal-vulnerable but is documented as not RCE-capable through this gadget; the RCE workflow requires setup with 16.2.x or the specified 15.x range plus the intentionally unsafe higher-order Server Action in app/app/page.js.FORTBRIDGE-UK · Disclosed Sep 3, 2026 · javascript · powershell · web · networkOperational
FAQ

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.
Activity feed

Recent activity

59 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
empirical security blogNews · Oct 1, 2026October 2026 CVE of the Month: The Next.js RCE Behind "Not Affected" (CVE-2026-75604) | Empirical SecurityA Windows-specific Next.js cache path-traversal vulnerability, rated CVSS 9.0, can expose the Server Actions encryption key and enable unauthenticated remote code execution under additional application conditions. Affected versions begin at 13.4.0, with fixes in 15.5.24 and 16.3.3. The article highlights a scope discrepancy: the CVE record says Pages Router or App Router, while the vendor advisory and public exploit require both, with Cache Components disabled and the default filesystem cache. A public Metasploit module exists. The publisher reports exploitation telemetry beginning September 18, 2026, most recently September 24, while acknowledging some activity could be testing. Recommended defenses include upgrading, blocking encoded backslashes at the WAF or proxy, and rotating exposed Server Actions keys after deploying the fix.Read more ↗ghsa syntheticNews · Sep 8, 2026GHSA-p293-qw3h-jr36An unauthenticated remote code execution vulnerability in Next.js applications using the Pages Router or App Router without Cache Components when hosted on servers using a Windows filesystem.Read more ↗fortbridge blogNews · Sep 4, 2026Next.js Path Traversal to RCE (CVE-2026-75604)A Windows-specific Next.js incremental-cache path traversal caused by failure to escape backslash characters in cached route paths. Percent-encoded backslashes can escape the cache root, enabling unauthenticated arbitrary file reads and writes accessible to the server process. Reading the Server Action encryption key can enable forged Server Action arguments, authorization bypass, and, in susceptible versions with a dangerous higher-order Server Action pattern, remote code execution.Read more ↗tenable nessus pluginsNews · Sep 3, 2026Next.js Framework 13.4 < 15.5.24 / 16.x < 16.3.3 RCE (Windows) | Tenable®A high-impact network-reachable vulnerability in Vercel Next.js that requires high attack complexity but no privileges or user interaction. Successful exploitation can affect confidentiality, integrity, and availability at high impact, including across a security scope boundary.Read more ↗
+11 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signatures1YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity40Community discussion across Reddit, Mastodon, and other social sources.