Skip to main content
Report · SecurityWeekAbout CVE-2025-55182Published

Exploitation of React2Shell Surges

Source SecurityWeek

0
Authoritative record:CVE-2025-55182· Critical 10.0

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 26 Oct 2026, 08:30 UTC

CVSS 3.1 base score
10.0Critical
How severe the flaw is on the 0–10 CVSS scale.
KEV deadline
 US federal agencies must patch by this date; a sensible deadline for everyone else.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 3 Dec 2025

  2. Exploited in the wild: evidence found.

    Listed in CISA KEV 2 days after disclosure

  3. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by Meta Platforms, Inc.

    , 117 days before disclosure

  2. CVE published

    on cve.org

    , t = 0

  3. In Threat Radar

    record ingested

    , 14 minutes after disclosure

  4. Added to CISA KEV (opens in a new tab)

    exploitation confirmed · ransomware use known

    , 2 days after disclosure

  5. KEV remediation due

    US federal deadline

    , 9 days after disclosure

  6. 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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Metareact-server-dom-webpackAffected
  • >=19.0.0 <=19.0.0
  • >=19.1.0 <=19.1.1
  • >=19.2.0 <=19.2.0
Fixed in–
Metareact-server-dom-turbopackAffected
  • >=19.0.0 <=19.0.0
  • >=19.1.0 <=19.1.1
  • >=19.2.0 <=19.2.0
Fixed in–
Metareact-server-dom-parcelAffected
  • >=19.0.0 <=19.0.0
  • >=19.1.0 <=19.1.1
  • >=19.2.0 <=19.2.0
Fixed in–
npmreact-server-dom-parcelpkg:npm/react-server-dom-parcelOther threatsAffected
  • =19.0.0
  • =19.1.0
  • =19.1.1
  • =19.2.0
Fixed in–
npmreact-server-dom-turbopackpkg:npm/react-server-dom-turbopackOther threatsAffected
  • =19.0.0
  • =19.1.0
  • =19.1.1
  • =19.2.0
Fixed in–
npmreact-server-dom-webpackpkg:npm/react-server-dom-webpackOther threatsAffected
  • =19.0.0
  • =19.1.0
  • =19.1.1
  • =19.2.0
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 implement a multi-layered mitigation strategy. First, monitor official React project channels and security advisories closely to apply patches immediately once available. Until patches are released, conduct thorough code audits focusing on input handling and component rendering logic to identify and remediate vulnerable patterns. Employ strict input validation and sanitization to prevent injection of malicious payloads. Deploy Web Application Firewalls (WAFs) with updated rules to detect and block exploitation attempts targeting React2Shell. Enhance logging and monitoring of web application behavior to identify anomalous activities indicative of exploitation. Educate development teams about secure coding practices specific to React and the nature of this vulnerability. Consider isolating critical React applications in segmented network zones to limit potential lateral movement. Finally, prepare incident response plans tailored to web application compromises involving React vulnerabilities to ensure rapid containment and remediation.

Description

An increasing number of threat actors have been attempting to exploit the React vulnerability CVE-2025-55182 in their attacks. The post Exploitation of React2Shell Surges appeared first on SecurityWeek .

References

Community reviews

Loading reviews…