Vigilbase CVEConnect your agent

Meta React Server Components Remote Code Execution Vulnerability

Exploited · KEV 2025-12-05RansomwareMetasploit moduleCVE-2025-55182

Exploited since 2025-12-05. 5 of 8 rule sources name it; Cloudflare blocks by default. Our CRS test: blocked.

Edge rules
5/8
Our test
Blocked
CVSS
10.0
EPSS
99.8% Top 0.1%
Posts, 14d
02026-10-20: 0 posts2026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 0 posts
Published
2025-12-03
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… More

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.

Ask Vigil

AI · answers from this page
Ask about CVE-2025-55182: who's covered, what to patch first, how vendors compare. I cite sources and won't help with attacks.

Workers AI (Llama 3.3). Can be wrong: check the cited source.

Severity, decoded

CVSS 3.1
Critical · 10.0 / 10

Exploitable over the network, with no privileges and no user interaction, leading to full loss of confidentiality, integrity and availability, and the impact can reach components beyond the vulnerable one.

Over the internetNo login neededNo user actionWorks reliablySpreads beyond the appFull compromise
How the score is built8 metrics
  • Attack vectorAn attacker can reach it over the internet; no access to your network needed.
    Network
  • Attack complexityNo special conditions are needed; the attack works reliably.
    Low
  • Privileges requiredNo account or login is needed.
    None
  • User interactionNo one has to click or open anything; the attack works on its own.
    None
  • ScopeThe attack can spread beyond the vulnerable component to other parts of the system.
    Changed
  • Confidentiality impactAn attacker can read all data the affected component holds, or the most sensitive parts of it.
    High
  • Integrity impactAn attacker can change any data or files the affected component protects.
    High
  • Availability impactAn attacker can take the component down completely or keep it from serving anyone.
    High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
CISA's assessmentSSVC, from the CVE record
ExploitationActive

Attackers are exploiting this in the wild.

AutomatableYes

Attackers can script the attack end to end and hit many targets at once.

Technical impactTotal

A successful attack gives full control over the affected software or all of its data.

Public exploits

3 found
1 Metasploit1 Exploit-DB1 Scanner template0 GitHub PoCs

Links are to third-party code: never run it outside an isolated lab.

Timeline

  1. 2025-12-03
    CVE published
    CVE List
  2. 2025-12-03
    Metasploit module published
    Unauthenticated RCE in React Server Components (React2Shell)
  3. 2025-12-03
    Google Cloud ships a rule
    cve-canary
  4. 2025-12-03
    Cloudflare rule names it
    Earliest entry we can see is an update
  5. 2025-12-04
    F5 ships a rule
    React Server Components RCE
  6. 2025-12-05
    Added to CISA KEV
    Confirmed exploitation in the wild
  7. 2026-01-05
    OWASP CRS ships a rule
    feat(934100): added sequence for CVE-2025-55182 POCs (https://github.com/coreruleset/coreruleset/pull/4372)
  8. 2026-04-09
    Exploit published on Exploit-DB
    React Server 19.2.0 - Remote Code Execution
  9. 2026-11-02
    Our test: OWASP Core Rule Set blocked it
    paranoia level 1, anomaly threshold 5, default CRS settings
  10. 2026-11-02
    Our test: OWASP Core Rule Set blocked it
    paranoia level 2, anomaly threshold 5, default CRS settings

Social

2026-10-20: 0 posts2026-10-21: 0 posts2026-10-22: 0 posts2026-10-23: 0 posts2026-10-24: 0 posts2026-10-25: 0 posts2026-10-26: 0 posts2026-10-27: 0 posts2026-10-28: 0 posts2026-10-29: 0 posts2026-10-30: 0 posts2026-10-31: 0 posts2026-11-01: 0 posts2026-11-02: 0 posts

No posts seen yet on X, Bluesky, Mastodon, Hacker News or GitHub.

Vendor statements

Quoted
CloudflareWAF Managed Rules4 quotesBlocks by default

Named by 2025-12-03; the first entry is an update, so the rule may be older.

2025-12-03Updated…5fb92fbaDefault: BlockSource
React - RCE - CVE:CVE-2025-55182. Previous action: N/A. New action: Block. Rule metadata description changed. Detection unchanged.
2025-12-03Updated…99702280Default: BlockSource
React - RCE - CVE:CVE-2025-55182. Previous action: N/A. New action: Block. Rule metadata description changed. Detection unchanged.
2025-12-10Updated…15fce168Default: BlockSource
React - Remote Code Execution - CVE:CVE-2025-55182 - 2. Previous action: N/A. New action: Block. This is an improved detection.
2025-12-10Updated…74746affDefault: BlockSource
React - Remote Code Execution - CVE:CVE-2025-55182 - 2. Previous action: N/A. New action: Block. This is an improved detection.
AWSAWS WAF Managed RulesNo public claim

We found no public statement from this vendor naming this CVE. That is not proof of no protection: generic rules may still catch it. AWS often describes a vulnerability without naming its CVE (for example "Log4j"). We count only entries that name the CVE, so AWS coverage is understated.

Microsoft AzureFront Door and Application Gateway WAF (DRS)2 quotesRule published
UndatedListed99001018Source
Rule 99001018: Critical - 5 · 1 · Attempted React2Shell remote code execution exploitation CVE-2025-55182
UndatedListed800115Source
Rule 800115: Critical - 5 · PL1 · Attempted React2Shell remote code execution exploitation CVE-2025-55182
Google CloudCloud Armor preconfigured WAF rules4 quotesRule published

First rule 2025-12-03, the day the CVE was published.

2025-12-03New rulecve-canarySource
Security The Cloud Armor cve-canary rules include the google-mrs-v202512-id000001-rce signature to help detect and mitigate CVE-2025-55182 .
2025-12-06New rulecve-canarySource
Security The Cloud Armor cve-canary rules include the google-mrs-v202512-id000002-rce signature to help detect and mitigate CVE-2025-55182 .
UndatedListed…0001-rceSource
Signature google-mrs-v202512-id000001-rce (sensitivity 0): React RCE vulnerability to help detect and mitigate CVE-2025-55182
UndatedListed…0002-rceSource
Signature google-mrs-v202512-id000002-rce (sensitivity 0): React RCE vulnerability to help detect and mitigate CVE-2025-55182
FastlyNext-Gen WAF virtual patchesBefore feed history

The CVE predates the oldest entry in this vendor's public feed, so a rule may exist that we cannot see.

F5Attack signatures (Distributed Cloud WAF)3 quotesRule published

First rule 2025-12-04, 1 day after the CVE was published.

2025-12-04New rule200204048Source
Added: signature 200204048 "React Server Components RCE" (Server Side Code Injection, risk High), systems: Node.js, JavaScript, ReactJS. References: CVE-2025-55182, CVE-2025-66478.
2025-12-12Updated200204048Source
Updated: signature 200204048 "React Server Components RCE" (Server Side Code Injection, risk High), systems: Node.js, JavaScript, ReactJS. References: CVE-2025-55182, CVE-2025-66478.
2025-12-12Updated200204050Source
Updated: signature 200204050 "Next.js RSC Remote Code Execution" (Server Side Code Injection, risk High), systems: Node.js, JavaScript, ReactJS. References: CVE-2025-55182, CVE-2025-66478.
AkamaiApp & API Protector (Adaptive Security Engine)No public source

This vendor publishes no machine-readable rule changelog we can check.

OWASP CRSCore Rule Set (open source, used inside many WAFs)1 quoteRule published

First rule 2026-01-05, 33 days after the CVE was published.

2026-01-05New rule934100Source
feat(934100): added sequence for CVE-2025-55182 POCs (https://github.com/coreruleset/coreruleset/pull/4372)