Is there a public exploit for CVE-2025-55182?

Yes. CVE-2025-55182 is listed in the CISA Known Exploited Vulnerabilities catalog, meaning exploitation has been observed in the wild.

Is there a proof of concept for CVE-2025-55182?

Yes — 8 proof-of-concept entries are linked on this page, from public repositories and community submissions. They are listed for authorised testing only.

How severe is CVE-2025-55182?

CVE-2025-55182 scores CVSS 10 (v3.1), rated critical. EPSS puts the chance of exploitation in the next 30 days at 99.8%.

What does CVE-2025-55182 affect?

CVE-2025-55182 affects Meta React Server Components.

10.0 Critical

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…

CVE-2025-55182 Exploited

Impact There is an unauthenticated remote code execution vulnerability in React Server Components. We recommend upgrading immediately. The vulnerability is present in versions 19.0.0, 19.1.0, 19.1.1, and 19.2.0 of: [react-server-dom-webpack](https://www.npmjs.com/package/react-server-dom-webpack) [react-server-dom-parcel](https://www.npmjs.com/package/react-server-dom-parcel) [react-server-dom-turbopack](https://www.npmjs.com/package/react-server-dom-turbopack?activeTab=readme) Patches A fix was introduced in versions [19.0.1](https://github.com/facebook/react/releases/tag/v19.0.1), [19.1.2](https://github.com/facebook/react/releases/tag/v19.1.2), and [19.2.1](https://github.com/facebook/react/releases/tag/v19.2.1). If you are using any of the above packages please upgrade to any of the fixed versions immediately. If your app’s React code does not use a server, your app is not affected by this vulnerability. If your app does not use a framework, bundler, or bundler plugin that supports React Server Components, your app is not affected by this vulnerability. References See the [blog post](https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components)…

Being exploited in the wild

Catalogued 5 December 2025 · US federal remediation deadline 12 December 2025 · Known use in ransomware campaigns

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Exploit code is also public: Metasploit · Exploit-DB · Public PoC · Nuclei template

Metasploitexploit/multi/http/react2shell_unauth_rce_cve_2025_55182
Exploit-DBReact Server 19.2.0 - Remote Code Execution
NucleiReact Server Components - Remote Code Execution
Public PoCassetnote/react2shell-scanner2,452 stars
Public PoCmsanft/CVE-2025-551821,433 stars
Public PoClachlan2k/React2Shell-CVE-2025-55182-original-poc1,067 stars
Public PoCejpir/CVE-2025-55182-research789 stars
Public PoCmrknow001/RSC_Detector584 stars
Public PoCemredavut/CVE-2025-55182314 stars
Public PoCzack0x01/CVE-2025-55182-advanced-scanner-281 stars
Public PoCynsmroztas/NextRce267 stars

Assessment

CVSS: 10 (v3.1)
Severity: Critical
EPSS: 99.8% chance of exploitation in the next 30 days
Known exploited: Yes — listed in the CISA KEV catalog
Exploit availability: CISA KEV, Metasploit, Exploit-DB, Public PoC, Nuclei template
Published: 3 December 2025
Last updated: 18 October 2026
Affected: Meta · React Server Components · react-server-dom-parcel · react-server-dom-turbopack · react-server-dom-webpack · react-server-dom-webpack · react-server-dom-turbopack · react-server-dom-parcel
Weakness: CWE-502
Assigner: cve-assign@fb.com

CVSS vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept

Only for publicly disclosed vulnerabilities, and only material from testing you were authorised to perform. This platform does not buy, sell, or broker exploits — see earning from vulnerability research for legitimate bounty programs. Submissions are reviewed before they appear. Text only; do not include live credentials, personal data, or anything targeting systems you are not permitted to test.

Title *

Proof of concept *

Write-up (optional)

Affected versions (optional)

Name or handle (optional)

References (optional, one URL per line)

Licence for your contribution *

Private contact (optional, never shown)

Before you submit * This vulnerability is already publicly disclosed (it has a published CVE). This material comes only from testing I was authorised to perform. I have the legal right to publish this content and am not breaching any agreement by doing so. It contains no live credentials, personal data, or anything targeting systems I am not authorised to test. I understand it will be reviewed before it appears publicly and may be rejected. I agree to the submission terms.

What is 8 + 1? *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2025-55182