CVE-2025-55182 Meta React Server Components Remote Code Execution Vulnerability
Meta React Server Components contains a remote code execution vulnerability that could allow unauthenticated remote code execution by exploiting a flaw in how React decodes payloads sent to React Server Function endpoints. Please note CVE-2025-66478 has been rejected, but it is associated with CVE-2025- 55182.
From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.
Should You Worry?
- CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 5 Dec 2025.
- CISA lists it as known to be used in ransomware campaigns.
- Rated Critical severity (CVSS 10.0, scored by Vendor).
- It has been in the catalogue for 336 days. Systems still unpatched now have almost certainly been scanned for it.
What It Is
A pre-authentication remote code execution vulnerability exists in React Server Components versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 including the following packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. The vulnerable code unsafely deserializes payloads from HTTP requests to Server Function endpoints.
Affected Versions
| Product | Versions |
|---|---|
| Meta react-server-dom-webpack | 19.0.0 to 19.0.0 19.1.0 to 19.1.1 19.2.0 to 19.2.0 |
| Meta react-server-dom-turbopack | 19.0.0 to 19.0.0 19.1.0 to 19.1.1 19.2.0 to 19.2.0 |
| Meta react-server-dom-parcel | 19.0.0 to 19.0.0 19.1.0 to 19.1.1 19.2.0 to 19.2.0 |
From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.
What To Do Now
- 1
Find it
Search your asset inventory and external attack surface for Meta React Server Components. Include cloud images, appliances and anything a supplier runs for you.
Attack Surface Management - 2
Fix it
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
Vulnerability Management - 3
Hunt for compromise
If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.
Incident Response - 4
Prove it is fixed
Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.
Penetration Testing
The Compliance Clock
General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.
More Exploited Meta Flaws
Not Sure If You Are Exposed?
Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2025-55182 and every other exploited flaw on the list.