CVE-2025-66478: React2Shell
CVE-2025-66478 was rejected as a duplicate of CVE-2025-55182, known as React2Shell. It originally tracked the downstream impact on Next.js of an unsafe deserialization vulnerability in the React Server Components Flight protocol. Crafted HTTP payloads processed by Server Function request handling can cause unauthenticated server-side JavaScript execution and operating-system command execution. Affected Next.js deployments use App Router with vulnerable React Server Components dependencies, including unpatched 15.x and 16.x releases and experimental canary releases beginning with 14.3.0-canary.77. The underlying affected React packages are react-server-dom-webpack, react-server-dom-parcel, and react-server-dom-turbopack versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0.
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 application confidentiality, integrity, and availability through arbitrary code execution with the application process's privileges. Attackers can steal application secrets, cloud credentials, database credentials, and user data; modify application behavior; deploy malware or persistence; and potentially pivot into accessible internal services. Active exploitation has included credential harvesting, cryptomining, backdoors, and proxy tunnels. Root or administrator access is not inherent and depends on process privileges or additional exploitation.
Mitigation
If you can’t patch tonight, do this now.
Use vendor-provided WAF protections as a temporary measure and defense in depth, not as a substitute for upgrading. AWS WAF users can enable AWSManagedRulesKnownBadInputsRuleSet version 1.24 or an appropriate later version containing the relevant protection, or deploy and test the vendor-provided custom blocking rule. Monitor application and endpoint telemetry for suspicious child processes spawned by Node.js and anomalous Server Function requests. Scanning and exploitation can produce similar application errors, so error signatures alone do not establish successful compromise.
Remediation
Patch, then assume compromise.
Upgrade affected Next.js deployments to a patched release in the applicable release line: 15.0.5, 15.1.9, 15.2.6, 15.3.6, 15.4.8, 15.5.7, or 16.0.7, or a later supported security release. For experimental canary deployments, follow the corresponding vendor upgrade guidance. Independently managed affected React Server Components packages should be upgraded to 19.0.1, 19.1.2, or 19.2.1, or later patched releases. Rebuild and redeploy affected applications, and verify the deployed dependency versions. Investigate potentially exposed deployments for compromise and revoke or rotate exposed secrets; patching alone does not remove existing attacker access.
Exploits
57 exploits validated by Mallory's analysis. Hidden: 105 rejected by Mallory's analysis as not a working exploit; 2 not yet analyzed, such as Exploit-DB entries. Showing the 25 most capable, earliest first.
References
Frequently asked questions
- Is CVE-2025-66478 exploited in the wild?
- Yes. As of Nov 19, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2025-66478?
- Yes. Mallory tracks 57 public exploits or proofs of concept for CVE-2025-66478, the earliest disclosed Jul 15, 2025.
- Is there a patch for CVE-2025-66478?
- Upgrade affected Next.js deployments to a patched release in the applicable release line: 15.0.5, 15.1.9, 15.2.6, 15.3.6, 15.4.8, 15.5.7, or 16.0.7, or a later supported security release. For experimental canary deployments, follow the corresponding vendor upgrade guidance.
Recent activity
238 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.