CVE-2025-55182 — Meta React Server Components Remote Code Execution Vulnerability
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Used in ransomware campaigns (CISA)+10
- Exploited by 1 threat actor(s) (MITRE ATT&CK)+10
- Public exploit/PoC (nuclei, metasploit, exploitdb, github)+20
- EPSS 99.8% (30-day exploitation probability)+15
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented patch — react.dev (NIST National Vulnerability Database)
- Documented patch — www.openwall.com (NIST National Vulnerability Database)
- Npm React-server-dom-webpack: fixed in version 19.1.2 — github.com (GitHub Security Advisories)
- Npm React-server-dom-webpack: fixed in version 19.2.1 — github.com (GitHub Security Advisories)
- Npm React-server-dom-webpack: fixed in version 19.0.1 — github.com (GitHub Security Advisories)
- Npm React-server-dom-turbopack: fixed in version 19.1.2 — github.com (GitHub Security Advisories)
- Npm React-server-dom-turbopack: fixed in version 19.2.1 — github.com (GitHub Security Advisories)
- Npm React-server-dom-turbopack: fixed in version 19.0.1 — github.com (GitHub Security Advisories)
- Npm React-server-dom-parcel: fixed in version 19.1.2 — github.com (GitHub Security Advisories)
- Npm React-server-dom-parcel: fixed in version 19.2.1 — github.com (GitHub Security Advisories)
- Npm React-server-dom-parcel: fixed in version 19.0.1 — github.com (GitHub Security Advisories)
CISA required action CISA
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
US federal deadline: Dec 12, 2025 — passed 307 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Facebook React, Meta React-server-dom-parcel, Meta React-server-dom-turbopack…).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the fixed version or the patch documented under Remediation.
- EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes matching the vulnerability class (insecure deserialization), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| React | version 19.1.0version 19.1.1version 19.2.0version 19.0.0 | Vulnerable | NIST National Vulnerability Database | |
| Meta | React-server-dom-parcel | ≥ 19.2.0 and ≤ 19.2.0≥ 19.1.0 and ≤ 19.1.1≥ 19.0.0 and ≤ 19.0.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Meta | React-server-dom-turbopack | ≥ 19.2.0 and ≤ 19.2.0≥ 19.1.0 and ≤ 19.1.1≥ 19.0.0 and ≤ 19.0.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Meta | React-server-dom-webpack | ≥ 19.2.0 and ≤ 19.2.0≥ 19.1.0 and ≤ 19.1.1≥ 19.0.0 and ≤ 19.0.0 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Vercel | Next.js |
version 15.6.0-canary38version 15.6.0-canary48version 15.6.0-canary47version 15.6.0-canary46version 15.6.0-canary45version 15.6.0-canary44version 15.6.0-canary43version 15.6.0-canary42 and 70 moreversion 15.6.0-canary41version 15.6.0-canary40version 15.6.0-canary4version 15.6.0-canary39version 15.6.0-canary51version 15.6.0-canary37≥ 15.3.0 and < 15.3.6version 15.6.0-canary35version 15.6.0-canary34version 15.6.0-canary33version 15.6.0-canary57≥ 15.0.0 and < 15.0.5≥ 15.1.0 and < 15.1.9≥ 15.2.0 and < 15.2.6version 16.0.0version 15.6.0-canary9version 15.6.0-canary8version 15.6.0-canary7version 15.6.0-canary6version 15.6.0-canary49version 15.6.0-canary56version 15.6.0-canary55version 15.6.0-canary54version 15.6.0-canary53version 15.6.0-canary52version 15.6.0-canary36version 15.6.0-canary50version 15.6.0-canary5version 14.3.0-canary83version 15.6.0-canary12version 15.6.0-canary11version 15.6.0-canary10version 15.6.0-canary32version 15.6.0-canary0version 15.6.0version 14.3.0-canary87version 14.3.0-canary86version 14.3.0-canary85version 14.3.0-canary84version 15.6.0-canary1version 14.3.0-canary82version 14.3.0-canary81version 14.3.0-canary80version 14.3.0-canary79version 14.3.0-canary78version 14.3.0-canary77≥ 16.0.0 and < 16.0.7≥ 15.5.0 and < 15.5.7≥ 15.4.0 and < 15.4.8version 15.6.0-canary14version 15.6.0-canary31version 15.6.0-canary30version 15.6.0-canary3version 15.6.0-canary29version 15.6.0-canary28version 15.6.0-canary27version 15.6.0-canary26version 15.6.0-canary25version 15.6.0-canary24version 15.6.0-canary23version 15.6.0-canary13version 15.6.0-canary15version 15.6.0-canary16version 15.6.0-canary17version 15.6.0-canary18version 15.6.0-canary19version 15.6.0-canary2version 15.6.0-canary20version 15.6.0-canary22version 15.6.0-canary21 |
Vulnerable | NIST National Vulnerability Database |
| Npm | React-server-dom-parcel | version 19.0.0version 19.2.0≥ 19.1.0 and < 19.1.2 | Vulnerable | GitHub Security Advisories |
| Npm | React-server-dom-turbopack | version 19.0.0version 19.2.0≥ 19.1.0 and < 19.1.2 | Vulnerable | GitHub Security Advisories |
| Npm | React-server-dom-webpack | version 19.0.0version 19.2.0≥ 19.1.0 and < 19.1.2 | Vulnerable | GitHub Security Advisories |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 10.0 | CVSS 3.1 | Critical | 3.9 | 6.0 | cve-assign@fb.com via NIST National Vulnerability Database |
| 10.0 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 10.0 | CVSS 3.1 | Critical | — | — | Meta via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (score shown at the top: cve-assign@fb.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- Unauthenticated RCE in React Server Components (React2Shell) excellent Dec 3, 2025
- React Server 19.2.0 - Remote Code Execution Apr 9, 2026
- High Fidelity Detection Mechanism for RSC/Next.js RCE (CVE-2025-55182 & CVE-2025-66478) ★ 2453 Dec 4, 2025
- Explanation and full RCE PoC for CVE-2025-55182 ★ 1431 Dec 4, 2025
- Original Proof-of-Concepts for React2Shell CVE-2025-55182 ★ 1063 Dec 5, 2025
- CVE-2025-55182 POC ★ 790 Dec 3, 2025
- Supports RSC fingerprinting and exploitation of the React component vulnerability CVE-2025-55182. ★ 587 Dec 5, 2025
- RSC/Next.js RCE Vulnerability Detector & PoC Chrome Extension – CVE-2025-55182 & CVE-2025-66478 ★ 313 Dec 6, 2025
- zack0x01/CVE-2025-55182-advanced-scanner- ★ 282 Dec 6, 2025
- React Shell & Next.js RSC Exploit Tool (CVE-2025-55182) ★ 266 Dec 6, 2025
- RSC Detect CVE 2025 55182 ★ 190 Feb 25, 2026
- Exploit for CVE-2025-55182 & CVE-2025-66478 ★ 142 Dec 5, 2025
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
Threat actors exploiting this CVE MITRE ATT&CK
According to MITRE ATT&CK.
TeamPCP G1056EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 99.80%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Monitor serialized objects in requests and unexpected processes spawned by the runtime.
- Hunt retroactively in logs from before Dec 5, 2025 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · meta/react-server-dom-webpack, meta/react-server-dom-turbopack, meta/react-server-dom-parcel
- SSVC assessment updated
- Fix documented
- Affected products added · npm/react-server-dom-webpack, npm/react-server-dom-turbopack, npm/react-server-dom-parcel
- Record published
- Fix documented
- Affected products added · facebook/react, vercel/next.js
- CVSS changed · 10.0
- Source status changed · → Analyzed
- Added to CISA KEV (detected)
- Record created in this database
- 2025
- Added to CISA KEV catalog
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 2× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
15 on the record
- www.facebook.com/security/advisories/cve-2025-55182
- www.openwall.com/lists/oss-security/2025/12/03/4
- react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-compo
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- nvd.nist.gov/vuln/detail/CVE-2025-55182
- github.com/advisories/GHSA-fv66-9v8q-g76r
- github.com/facebook/react/releases/tag/v19.2.1
- aws.amazon.com/blogs/security/china-nexus-cyber-threat-groups-rapidly-exploit-react2
- news.ycombinator.com/item
- github.com/facebook/react/releases/tag/v19.1.2
- github.com/facebook/react/pull/35277
- github.com/ejpir/CVE-2025-55182-poc
- github.com/facebook/react/commit/7dc903cd29dac55efb4424853fd0442fef3a8700
- github.com/facebook/react/releases/tag/v19.0.1
- github.com/facebook/react/security/advisories/GHSA-fv66-9v8q-g76r
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-94543 Next.js: Cache poisoning of SSG and ISR pages in self-hosted Next.js applications 13d
- Medium CVE-2026-94483 Next.js: Server-Side Request Forgery in Image Optimization 13d
- Medium CVE-2026-64648 Next.js is a React framework for building full-stack web applications. In versions… Jul 27, 2026
- Medium CVE-2026-64649 Server-Side Request Forgery (SSRF) in Vercel Next.js Jul 27, 2026
- Medium CVE-2026-64646 Allocation of Resources Without Limits or Throttling in Vercel Next.js Jul 27, 2026
- Medium CVE-2026-64647 Improper Encoding or Escaping of Output in Vercel Next.js Jul 27, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-55182 is "Meta React Server Components Remote Code Execution Vulnerability", rated Critical. It affects React (Facebook); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 10.0 describes technical severity. EPSS 99.80% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.