CVE-2025-55182 vulnerability in React and Next.js | Kaspersky official blog
Source Kaspersky Security Blog
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 16 Nov 2026, 20:25 UTC
- KEV deadline
- US federal agencies must patch by this date; a sensible deadline for everyone else. Other KEV due dates
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
Weaponized: 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 16 Nov 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 immediately update all React Server Components packages to versions 19.0.1, 19.1.2, or 19.2.1 and Next.js to versions 15.1.9, 15.2.6, 15.3.6, 15.4.8, 15.5.7, or 16.0.7 to remediate the vulnerability. They must inventory all applications using React RSC and Next.js to identify vulnerable instances, including indirect dependencies in derivative frameworks. Deploy and verify activation of WAF rules from cloud providers or third-party vendors to provide immediate protection, but do not rely solely on these. Restrict access to RSC endpoints by implementing strict IP whitelisting, reputation-based filtering, and rate limiting, especially for internal services. Enhance monitoring by deploying EDR/EPP solutions on servers hosting RSC components to detect anomalous process execution and post-exploitation behaviors such as secret reconnaissance and web shell deployment. Conduct thorough log analysis for suspicious HTTP requests indicative of exploitation attempts. Rotate all secrets, API keys, and credentials stored or accessible on affected servers as a precautionary measure. Educate development teams on secure deserialization practices and review application architectures to minimize exposure of server-side components. Finally, establish incident response plans tailored to this vulnerability to enable rapid containment and remediation if exploitation is detected.
Description
CVE-2025-55182, dubbed React4Shell, is a critical remote code execution vulnerability affecting React Server Components (RSC) and related frameworks such as Next.js. It allows unauthenticated attackers to send specially crafted HTTP requests that trigger unsafe deserialization in the Flight protocol, leading to arbitrary code execution on the server. The vulnerability impacts multiple React server-dom packages and several Next.js versions widely used in modern web applications. Exploitation requires no authentication or user interaction and can result in complete server takeover. Although no confirmed in-the-wild exploitation has been reported, proof-of-concept exploits exist, and the vulnerability affects approximately 39% of cloud infrastructures hosting React-based sites. Major cloud providers have deployed WAF rules to mitigate attacks, but patching remains essential. European organizations using vulnerable React or Next.js versions must urgently update, apply WAF protections, restrict server access, and monitor for suspicious activity to prevent potential large-scale attacks.