React2Shell Remote Code Execution Vulnerability in React 19 and Next.js
A critical remote code execution vulnerability, dubbed React2Shell, was discovered in the React 19 library, specifically affecting React Server Components. The flaw allows unauthenticated attackers to execute arbitrary code on servers by sending crafted requests, making it a severe risk for organizations using default React and Next.js deployments. Within hours of public disclosure, security firms including Google’s Threat Intelligence Group and AWS confirmed active exploitation in the wild, highlighting the shrinking window between vulnerability awareness and real-world attacks. Researchers from Wiz and Unit 42 demonstrated that even clean, default deployments were susceptible, emphasizing the widespread impact due to the popularity of these frameworks.
Threat actors rapidly weaponized the React2Shell vulnerability, with the RondoDoX botnet launching automated exploitation campaigns targeting both web applications and IoT devices. CloudSEK’s analysis of command and control logs revealed a multi-month campaign, with a significant spike in attacks following the vulnerability’s disclosure in December 2025. The RondoDoX botnet deployed various payloads, including web shells and cryptominers, and quickly adapted its infrastructure in response to security firm reports. Organizations with technology stacks overlapping the targeted vectors were promptly alerted, underscoring the urgent need for patching and monitoring in environments using React 19 and Next.js.
Timeline
Dec 31, 2025
CISA adds CVE-2025-55182 to the KEV catalog
By December 31, 2025, reporting noted that CISA had added CVE-2025-55182 to its Known Exploited Vulnerabilities catalog. The listing underscored that the flaw was actively exploited and required urgent remediation.
Dec 31, 2025
State-linked actors tied to React2Shell exploitation
Reporting in late December 2025 linked both criminal and state-aligned actors to React2Shell exploitation, including China-linked groups Earth Lumia and Jackpot Panda and North Korean operators. The flaw was described as being used for both initial access and persistent compromise.
Dec 31, 2025
Widespread exposure of vulnerable React2Shell systems reported
By late December 2025, researchers and internet scanning data reported tens of thousands of exposed vulnerable systems, with estimates ranging from about 77,000 in early December to more than 90,000 by the end of the month. Most exposed instances were reported in the United States.
Dec 29, 2025
Researchers confirm exploitation within hours of disclosure
Multiple vendors and researchers, including Google, AWS, Wiz, Unit 42, and Huntress, confirmed that React2Shell was exploited in the wild within hours of public disclosure. They also documented post-exploitation activity such as backdoors, tunneling tools, and cryptomining kits.
Dec 29, 2025
React and downstream frameworks release patches
React maintainers and downstream frameworks released patches for React2Shell and urged organizations to update immediately. Security guidance emphasized that patching should be paired with threat hunting because compromise could have already occurred.
Dec 29, 2025
React2Shell flaw is publicly disclosed as critical RCE
A critical unauthenticated remote code execution flaw in React 19 Server Components, tracked as CVE-2025-55182 and dubbed React2Shell, was publicly disclosed in December 2025. The bug affected default React and Next.js deployments and was rated CVSS 10.0.
Dec 13, 2025
Attackers shift infrastructure after React2Shell exposure
After Darktrace's December 10 reporting, RondoDox operators changed infrastructure, and CloudSEK observed new active command-and-control servers three days later. This indicated rapid adaptation to public scrutiny while continuing exploitation.
Dec 13, 2025
RondoDox begins repeated React2Shell attacks
CloudSEK observed exploitation of the Next.js/React Server Components flaw becoming the dominant RondoDox vector from December 13, 2025 onward. The botnet repeatedly delivered payloads including coinminers, Mirai-related binaries, and persistence tooling.
Dec 10, 2025
React2Shell exploitation publicly reported by Darktrace
CloudSEK said Darktrace publicly reported exploitation of React2Shell on December 10, 2025. This was an early public indication that attackers were already abusing the flaw in the wild.
Nov 1, 2025
RondoDox shifts to large-scale automated IoT deployment
By late 2025, the campaign had progressed from reconnaissance and web exploitation into hourly automated attacks that deployed botnet malware to IoT devices. Reports describe this as a distinct operational phase focused on scale, persistence, and propagation.
Jul 1, 2025
Fortinet first identifies RondoDox botnet activity
BleepingComputer said Fortinet first identified RondoDox in July 2025. By that point, the botnet had already been evolving its operations against exposed infrastructure.
Mar 1, 2025
RondoDox campaign begins reconnaissance and vulnerability testing
CloudSEK reported that the RondoDox botnet campaign started in March 2025 with reconnaissance and manual vulnerability testing against web applications and internet-exposed devices. This marked the first phase of a broader automated operation that later expanded to web servers and IoT targets.
See the full picture in Mallory
Mallory subscribers get deeper analysis on every story, including:
Who’s affected and how
Deep-dive technical analysis
Actionable next steps for your team
IPs, domains, hashes, and more
Ask questions and take action on every story
Filter by topic, classification, timeframe
Get matching stories delivered automatically
Related Entities
Vulnerabilities
Organizations
Sources
5 more from sources like securityaffairs, the hacker news, rescana blog, bleeping computer and cloudsek blog
Related Stories
Exploitation of React2Shell Vulnerability by Botnets and Threat Actors
A critical unauthenticated remote code execution (RCE) vulnerability, identified as React2Shell (`CVE-2025-55182`), was disclosed in December 2025, affecting applications built with React Server Components and related frameworks such as Next.js. Public proof-of-concept exploits were released shortly after disclosure, enabling attackers to inject and execute arbitrary code on vulnerable systems. Security researchers and vendors, including Sysdig, responded by publishing detection guidance and threat bulletins, urging organizations to patch affected software, update dependencies, and monitor for signs of compromise. The vulnerability's severity and ease of exploitation have made it a high-priority target for both opportunistic and advanced threat actors. Notably, botnet operators, including those behind the RondoDox botnet, have begun actively targeting the React2Shell flaw to compromise systems at scale. Security advisories recommend immediate patching and enhanced monitoring, as exploitation attempts have increased rapidly following the public release of exploit code. The incident underscores the ongoing risk posed by supply chain and framework vulnerabilities, especially when widely used components are affected and attackers move quickly to weaponize new flaws.
1 months ago
Active Exploitation of React2Shell (CVE-2025-55182) in React Server Components
Threat actors are actively exploiting **React2Shell** (**CVE-2025-55182**), a critical remote code execution flaw in the Flight protocol used for client-server communication in **React Server Components**. The issue is attributed to **insecure deserialization** that can allow unauthorized code execution on vulnerable servers, with observed targeting across insurance, e-commerce, and IT organizations. Reported payloads include the **XMRig** cryptocurrency miner as well as multiple botnets and remote access tooling; campaigns observed against Russian entities deployed **RustoBot** and **Kaiji**, while other activity distributed malware such as **CrossC2**, **Tactical RMM**, **VShell**, and **EtherRAT**. Affected packages include `react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack` in versions **19.0**, **19.1.0**, **19.1.1**, and **19.2.0**, with fixes available in **19.0.1**, **19.1.2**, and **19.2.1**. Separate reporting highlighted that attackers leveraged a **public proof-of-concept (PoC)** for React2Shell and began targeting organizations within hours, reinforcing that rapid weaponization is now common; defenders are advised to patch and also perform post-patch validation, including checking for indicators of compromise, verifying *Next.js* and dependency versions, rebuilding projects after updates, and confirming lockfiles no longer reference vulnerable package versions.
3 weeks ago
Exploitation of React2Shell Vulnerability (CVE-2025-55182) in IoT and Web Applications
A critical security vulnerability, React2Shell (CVE-2025-55182), affecting React Server Components and Next.js, has been widely exploited by both state-sponsored and criminal threat actors. The flaw enables unauthenticated remote code execution, making it a prime target for ransomware groups, botnet operators, and espionage campaigns throughout 2025. Notably, the RondoDox botnet leveraged this vulnerability in a persistent nine-month campaign to compromise IoT devices and web applications, enrolling tens of thousands of systems into its network. According to Shadowserver Foundation data, over 84,000 instances remained vulnerable as of early January 2026, with the majority located in the United States. PolySwarm's annual review highlights React2Shell as the year's most significant exploit, noting its rapid weaponization by both nation-state actors and cybercriminals. Ransomware groups such as Cl0p and Qilin used zero-day exploits, including React2Shell, to target enterprises, government, and healthcare sectors. The widespread abuse of this vulnerability underscores the urgent need for organizations to patch affected systems and monitor for signs of compromise, as attackers continue to exploit trusted software components for initial access and lateral movement.
1 months ago