Exploitation of React2Shell Surges
Source SecurityWeek
Exploited in the wild · KEV due 12 Dec 2025 · public exploit available (Metasploit, Exploit-DB) : apply the vendor's fix or mitigations to react-server-dom-webpack now.
Data as of 26 Oct 2026, 08:30 UTC
- KEV deadline
- US federal agencies must patch by this date; a sensible deadline for everyone else.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
t = 0 is the CVE’s publication on cve.org
Disclosed: evidence found.
CVE published 3 Dec 2025
Detectable: evidence found.
nuclei template: React Server Components - Remote Code Execution
Weaponised: evidence found.
1 Metasploit module · 1 Exploit-DB entry, 127 days after disclosure
Exploited in the wildExploited: evidence found.
Listed in CISA KEV 2 days after disclosure
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
Timeline
CVE ID reserved
by Meta Platforms, Inc.
, 117 days before disclosure
CVE published
on cve.org
, t = 0
In Threat Radar
record ingested
, 14 minutes after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed · ransomware use known
, 2 days after disclosure
KEV remediation due
US federal deadline
, 9 days after disclosure
First Exploit-DB entry (opens in a new tab)
React Server 19.2.0 - Remote Code Execution
, 127 days after disclosure
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CISA KEV (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Metareact-server-dom-webpack | Affected
| Fixed in– |
| Metareact-server-dom-turbopack | Affected
| Fixed in– |
| Metareact-server-dom-parcel | Affected
| Fixed in– |
npmreact-server-dom-parcelpkg:npm/react-server-dom-parcelOther threats | Affected
| Fixed in– |
npmreact-server-dom-turbopackpkg:npm/react-server-dom-turbopackOther threats | Affected
| Fixed in– |
npmreact-server-dom-webpackpkg:npm/react-server-dom-webpackOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
European organizations should implement a multi-layered mitigation strategy. First, monitor official React project channels and security advisories closely to apply patches immediately once available. Until patches are released, conduct thorough code audits focusing on input handling and component rendering logic to identify and remediate vulnerable patterns. Employ strict input validation and sanitization to prevent injection of malicious payloads. Deploy Web Application Firewalls (WAFs) with updated rules to detect and block exploitation attempts targeting React2Shell. Enhance logging and monitoring of web application behavior to identify anomalous activities indicative of exploitation. Educate development teams about secure coding practices specific to React and the nature of this vulnerability. Consider isolating critical React applications in segmented network zones to limit potential lateral movement. Finally, prepare incident response plans tailored to web application compromises involving React vulnerabilities to ensure rapid containment and remediation.
Description
An increasing number of threat actors have been attempting to exploit the React vulnerability CVE-2025-55182 in their attacks. The post Exploitation of React2Shell Surges appeared first on SecurityWeek .