Report · SecurityWeekAbout CVE-2025-55182Published 5 Dec 2025

Chinese Hackers Exploiting React2Shell Vulnerability

Source SecurityWeek

Authoritative record:CVE-2025-55182· Critical 10.0

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 8 Dec 2025, 12:01 UTC

CVSS base score

10.0Critical

How severe the flaw is on the 0–10 CVSS scale.

KEV deadline: 12 Dec 2025 US federal agencies must patch by this date; a sensible deadline for everyone else.

Exploitation 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

CVE ID reserved
by Meta
2025-08-0818:21Z, 117 days before disclosure
CVE published
on cve.org
2025-12-0315:40Z, t = 0
In Threat Radar
record ingested
2025-12-0315:54Z, 14 minutes after disclosure
Added to CISA KEV (opens in a new tab)
exploitation confirmed · ransomware use known
2025-12-05, 2 days after disclosure
KEV remediation due
US federal deadline
2025-12-12, 9 days after disclosure
First Exploit-DB entry (opens in a new tab)
React Server 19.2.0 - Remote Code Execution
2026-04-09, 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 2026-10-26.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Metareact-server-dom-webpack	Affected >=19.0.0 <=19.0.0 >=19.1.0 <=19.1.1 >=19.2.0 <=19.2.0	Fixed in–
Metareact-server-dom-turbopack	Affected >=19.0.0 <=19.0.0 >=19.1.0 <=19.1.1 >=19.2.0 <=19.2.0	Fixed in–
Metareact-server-dom-parcel	Affected >=19.0.0 <=19.0.0 >=19.1.0 <=19.1.1 >=19.2.0 <=19.2.0	Fixed in–
npmreact-server-dom-parcel`pkg:npm/react-server-dom-parcel`Other threats	Affected =19.0.0 =19.1.0 =19.1.1 =19.2.0	Fixed in–
npmreact-server-dom-turbopack`pkg:npm/react-server-dom-turbopack`Other threats	Affected =19.0.0 =19.1.0 =19.1.1 =19.2.0	Fixed in–
npmreact-server-dom-webpack`pkg:npm/react-server-dom-webpack`Other threats	Affected =19.0.0 =19.1.0 =19.1.1 =19.2.0	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Monitor official React and AWS security advisories closely for patches or updates addressing CVE-2025-55182 and apply them immediately upon release. 2. Implement enhanced logging and anomaly detection on AWS-hosted React applications to identify suspicious activities indicative of exploitation attempts. 3. Restrict network access to critical application components using AWS security groups and firewalls to limit exposure. 4. Conduct thorough code reviews and vulnerability assessments of React-based applications to identify and remediate insecure coding practices that could facilitate exploitation. 5. Employ runtime application self-protection (RASP) and web application firewalls (WAF) configured to detect and block exploit payloads targeting React vulnerabilities. 6. Enforce strict identity and access management (IAM) policies within AWS to minimize privileges and reduce lateral movement potential. 7. Educate development and security teams about the nature of React2Shell and encourage proactive threat hunting for early detection. 8. Prepare incident response plans specific to potential React2Shell exploitation scenarios to ensure rapid containment and recovery.

Description

AWS has seen multiple China-linked threat groups attempting to exploit the React vulnerability CVE-2025-55182. The post Chinese Hackers Exploiting React2Shell Vulnerability appeared first on SecurityWeek .

Impact

For European organizations, exploitation of the React2Shell vulnerability could result in significant operational and security impacts. Successful remote code execution could compromise confidentiality by exposing sensitive data, integrity by allowing unauthorized modifications, and availability by disrupting services. Organizations relying on React for customer-facing or internal applications, particularly those hosted on AWS, face increased risk of intrusion or service degradation. The threat is especially pertinent to sectors with high digital dependency such as finance, telecommunications, and government services. Additionally, exploitation attempts by China-linked groups suggest potential geopolitical motivations, increasing the likelihood of targeted attacks against strategic assets. The medium severity indicates that while immediate widespread damage is unlikely, the vulnerability could be leveraged for persistent access or as part of multi-stage attacks. European entities must consider the risk of reputational damage, regulatory penalties under GDPR for data breaches, and operational downtime.

Summary

The React2Shell vulnerability, designated CVE-2025-55182, is a security flaw in the React JavaScript library that potentially allows remote code execution (RCE) by attackers. This vulnerability arises from improper handling of certain inputs or components within React, enabling malicious actors to inject and execute arbitrary code on affected systems. AWS has reported multiple attempts by China-linked threat groups to exploit this vulnerability, indicating active targeting of cloud-hosted applications using React. Although no confirmed successful exploits have been documented, the attempts highlight the risk posed by this vulnerability. React is extensively used in web development, and many European organizations deploy React-based applications on AWS infrastructure, increasing their exposure. The exploitation could lead to unauthorized access, data theft, service disruption, or lateral movement within networks. The lack of available patches or detailed technical mitigations at this time complicates defense efforts. However, monitoring for unusual activity, applying any forthcoming patches promptly, and employing strict access controls can mitigate risk. The medium severity rating reflects the potential impact balanced against the current lack of confirmed exploitation and the complexity of successful attacks.

Public tooling indexed from Metasploit Framework, Exploit-DB and ProjectDiscovery nuclei-templates. Its existence raises the odds of exploitation; it does not confirm attacks.

References

securityweek.com/chinese-hackers-exploiting-react2shell-vulnerability/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

Timeline

What to do

Affected software

Description

AI analysisMachine-generated, updated 5 Dec 2025, 07:45 UTC

Public exploits and detection1 Metasploit module, 1 Exploit-DB entry, a Nuclei detection template

References

Community reviews

Related threats