Widespread React2Shell Vulnerability Detected
A critical vulnerability, identified as CVE-2025-55182 and commonly known as React2Shell, has triggered significant concern across the internet, leading to widespread outages and urgent security advisories.
New data from cybersecurity firm CyCognito reveals the extensive reach of this flaw across internet-facing applications, with a notable concentration within media organisations. The immediate and active exploitation of this vulnerability necessitates rapid response and patching across all affected systems.
CyCognito responded promptly to the emerging threat, issuing an Emerging Threat Advisory for CVE-2025-55182 (React2Shell) on 4 December 2025.
React2Shell Unpacked
CVE-2025-55182 (React2Shell) is a critical remote code execution (RCE) vulnerability, scoring a perfect 10.0 on the CVSS scale. It affects React Server Components (RSC) within React 19 and frameworks built upon it, including Next.js 15 and 16.
The flaw originates from unsafe deserialisation of untrusted data within the RSC Flight protocol. This allows malicious requests sent to a Server Function endpoint to manipulate the execution flow, enabling arbitrary JavaScript code to run on the server with the application's privileges.
Specific affected packages include versions of `react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack` up to and including 19.2.0. Even applications not explicitly using Server Functions may bundle these vulnerable components, presenting a considerable supply-chain risk.
Broad Exposure & Industry Impact
CyCognito's latest scan of externally exposed assets uncovered that approximately 18 percent were running vulnerable React Server Components. The distribution of this exposure is uneven across industries, with media organisations bearing a disproportionate burden.
These companies account for roughly 40 percent of the exposed assets in CyCognito's dataset, significantly ahead of other sectors such as manufacturing (16 percent) and professional services (10 percent). Technology, public sector environments, and hospitality also contribute to the affected landscape.
This elevated risk for media organisations appears to stem from their heavy reliance on server-rendered frameworks like Next.js to power critical public entry points such as homepages, article and video pages, and other high-traffic interfaces.
In these setups, React Server Components are integral for server-side data fetching and page composition, placing the vulnerable `react-server-dom-*` packages directly in the request path of exposed web assets. High-risk external assets further encompass publicly accessible web applications, SaaS environments handling sensitive data, and cloud workloads.
Emergency Measures
Confirmation of active exploitation for React2Shell emerged swiftly following its disclosure. By 4 December 2025, fully weaponised public exploits, including a Metasploit module, were readily available. On 5 December, the CISA added the vulnerability to its Known Exploited Vulnerabilities list, confirming that unpatched, externally reachable services should be considered potentially compromised from 3 December onwards.
The urgent nature of the threat was further highlighted on 5 December when Cloudflare deployed updated Web Application Firewall (WAF) request parsing to block React2Shell payloads. This mitigation effort inadvertently caused a brief global outage at 08:56 UTC, which was rolled back within minutes. The incident emphasises the immediate need for protective measures.
Urgent Remediation
Patches for CVE-2025-55182 were released on 3 December 2025, with framework vendors such as Next.js providing updated builds on the same day. Fixed versions include `react-server-dom-webpack`, `react-server-dom-parcel`, and `react-server-dom-turbopack` at 19.0.1, 19.1.2, and 19.2.1 respectively, among others. Next.js also published patched releases for the related CVE-2025-66478.
Organisations are urged to immediately upgrade all React RSC dependencies and frameworks to their patched releases.
Furthermore, they should rebuild and redeploy affected applications, and review logs from 3 December onwards for any indicators of scanning or exploitation attempts. Crucially, no configuration-only workaround fully removes the RCE risk; upgrading is essential.
Security teams should also discover and inventory all external React and Next.js applications, prioritise assets based on exposure and business impact, and deploy compensating controls like WAF rules targeting malicious RSC Flight payloads. Continuous monitoring for exploitation indicators, such as traffic spikes to RSC endpoints or unusual process execution, is vital.
CyCognito also advises customers to review all systems running Next.js, or associated web services, recognising that modern applications often contain hidden transitive dependencies. Given the ease of exploitation and the vast footprint across the internet, organisations must treat unpatched assets as being at significant risk and act decisively to secure their digital infrastructure.
CyCognito | Infosecurity Magazine | GovInfoSecurity | Wiz.io
Image: Ideogram
You Might Also Read:
Vulnerability Overload Is Pushing Security Teams To Exhaustion:
If you like this website and use the comprehensive 8,000-plus service supplier Directory, you can get unrestricted access, including the exclusive in-depth Directors Report series, by signing up for a Premium Subscription.
- Individual £5 per month or £50 per year. Sign Up
- Multi-User, Corporate & Library Accounts Available on Request
- Inquiries: Contact Cyber Security Intelligence
Cyber Security Intelligence: Captured Organised & Accessible






