CriticalCVE-2025-55182

    Meta React Server Components Remote Code Execution Vulnerability (CVE-2025-55182)

    Published Last modified In CISA KEV since Sources: CERT-EU, SingCERT, pwn.watch, CVE.org, OSV

    What is affected, what to do

    An attacker can perform remote code execution (RCE) without authentication by exploiting a deserialization flaw in React Server Components versions 19.0.0 to 19.2.0, affecting packages react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack. This vulnerability is actively exploited in ransomware campaigns. Immediate updating to the latest version is critical to mitigate this risk.

    The vulnerability is being actively exploited; treat it as a priority. CISA lists it as used in ransomware campaigns. Update next.js to version 15.0.5. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Meta React-server-dom-webpack lte 19.0.0..19.0.0
    • Meta React-server-dom-webpack lte 19.1.0..19.1.1
    • Meta React-server-dom-webpack lte 19.2.0..19.2.0
    • Meta React-server-dom-turbopack lte 19.0.0..19.0.0
    • Meta React-server-dom-turbopack lte 19.1.0..19.1.1
    • Meta React-server-dom-turbopack lte 19.2.0..19.2.0
    • Meta React-server-dom-parcel lte 19.0.0..19.0.0
    • Meta React-server-dom-parcel lte 19.1.0..19.1.1
    • Meta React-server-dom-parcel lte 19.2.0..19.2.0

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    10.0

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    10.0

    CVSS v3

    Severity Critical on the scale from 0 to 10.

    Source: CERT-EU, SingCERT, pwn.watch, CVE.org, OSV

    99.80 %

    EPSS score

    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.

    Source: FIRST EPSS, percentile 99.96

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    267.43 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploitedSource: VulnCheck KEV (opens in a new tab), ANSSI / CERT-FR How we classify
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    10.0 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    10.0
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    99.80 %
    High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    99.96
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 4 August 2026
    CWE

    CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.

    Read in glossary
    CWE-502

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This is an unauthenticated, no-interaction, scope-changing RCE that is network-reachable and triggered by a single HTTP request. It sits among the CVEs most likely to be exploited of any. Public exploits and mass scanning followed disclosure within days, and CISA flags known ransomware campaign use. Observed follow-on activity includes cryptominers, cloud-credential theft and initial access for later intrusions. Typical targets are web shops, customer portals and SaaS frontends built on Next.js App Router. Treat every internet-facing instance as critical with a remediation window measured in hours. Internal-only instances remain high priority but can follow within days.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Inventory dependencies: Search all repositories, container images and build artefacts for react-server-dom-webpack, react-server-dom-turbopack and react-server-dom-parcel at 19.0.0, 19.1.0, 19.1.1 or 19.2.0. Also search for next 15.0.0–15.0.5, 15.1.0–15.1.9, 15.2.0–15.2.6 and 15.3.0–15.3.6. Useful sources are npm ls react-server-dom-webpack next, SBOM queries and lockfile grep. Check other App Router-based Next.js lines against the vendor advisory.
      • Patch: Fixed releases are available from Meta/React and Vercel/Next.js. Look up the target version in each vendor advisory. Bump the lockfile, rebuild and redeploy. Updating source without rebuilding the image does not remove the vulnerable code.
      • Internet-facing first: Prioritise publicly reachable Next.js/RSC apps that use the App Router or Server Actions. If you cannot redeploy now, front the app with a WAF that has a rule for this CVE enabled, or take it offline temporarily.
      • Compromise assessment before patching: For any instance that was exposed and unpatched since early December 2025, preserve logs and the process tree. Hunt for the indicators below. Treat a positive hit as full host compromise.
      • Rotate secrets on suspicion: Rotate everything the Node.js process could read. That includes .env values, database credentials, API keys, cloud IAM role credentials reachable via the instance metadata service, and session/JWT signing keys.
    2. Runbook step 2

      Mitigation layers

      • WAF/IPS: Inspect POST requests that carry a Next-Action header or RSC payloads (text/x-component, or multipart/form-data sent to server-function routes). Block bodies containing prototype references such as __proto__ or constructor:constructor, or RSC reference patterns such as "$@, "$1: or :then". Enable the CDN/WAF providers' managed rules for CVE-2025-55182 and switch them from log mode to block mode.
      • Segmentation and egress filtering: Restrict outbound traffic from Node.js app servers to an allowlist of the database, internal APIs and required SaaS endpoints. Block arbitrary internet egress and reverse-shell ports. Enforce IMDSv2 with a hop limit to protect 169.254.169.254.
      • Endpoint/container hardening: Run Node.js as an unprivileged user with readOnlyRootFilesystem. Drop capabilities and enable seccomp/AppArmor. Prefer distroless images without a shell so attackers cannot easily stage tooling.
      • IAM/least privilege: Scope the workload identity tightly. Grant no bucket write access, no iam:* and no Secrets Manager wildcards. Use database accounts without DDL or admin rights.
      • Configuration: Remove or disable unused Server Actions/Functions. Put internal Next.js admin UIs behind VPN/ZTNA only.
    3. Runbook step 3

      Detection rules

      • EDR process ancestry: Alert on node or next-server spawning sh, bash, curl, wget, nc, python, base64 or chmod. Sigma shape: ParentImage|endswith: '/node' AND Image|endswith: ['/sh','/bash','/curl','/wget']. KQL: DeviceProcessEvents | where InitiatingProcessFileName =~ "node" and FileName in~ ("sh","bash","curl","wget","nc").
      • Linux auditd: Watch for execve events whose parent is the Node.js process. Rule: -a always,exit -F arch=b64 -S execve -F uid=<app-uid> -k rsc_exec. Any shell executed under the app user warrants investigation.
      • Web/reverse-proxy logs: Look for POSTs with a Next-Action header from unfamiliar sources, oversized multipart bodies, HTTP 500s following such POSTs, and sweeping scans across routes. SPL: index=web method=POST "Next-Action" | stats count by src_ip, uri | where count > 20.
      • Network telemetry (Zeek/Suricata): Flag first-seen outbound connections from app servers, metadata-endpoint access by Node processes, and DNS lookups for paste, tunnelling or mining services.
      • File and persistence artefacts: Watch for new executables in /tmp, /dev/shm or the app directory, and for edits to crontab or ~/.ssh/authorized_keys. Also flag shell processes reading .env (Sysmon for Linux EID 1/11).

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    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.

    Source: certeu_advisory, CSA/SingCERT, pwn.watch, NVD (NIST), cvelistv5, OSV (Open Source Vulnerabilities), CISA KEV Catalog, CVE.org (MITRE)

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    Metareact-server-dom-parcel
    • 19.1.0 – ≤ 19.1.1
    • ≤ 19.0.0
    • ≤ 19.2.0
    • —
    • —
    • —
    Metareact-server-dom-turbopack
    • ≤ 19.2.0
    • 19.1.0 – ≤ 19.1.1
    • ≤ 19.0.0
    • —
    • —
    • —
    Metareact-server-dom-webpack
    • ≤ 19.0.0
    • ≤ 19.2.0
    • 19.1.0 – ≤ 19.1.1
    • —
    • —
    • —
    facebookreact
    • 19.1.0
    • 19.1.1
    • 19.0.0
    • 19.2.0
    • —
    • —
    • —
    • —
    vercelnext.js
    • 15.6.0
    • 15.0.0 – < 15.0.5
    • 16.0.0
    • 14.3.0
    • 15.3.0 – < 15.3.6
    • 15.5.0 – < 15.5.7
    • 15.1.0 – < 15.1.9
    • 15.4.0 – < 15.4.8
    • 15.2.0 – < 15.2.6
    • 16.0.0 – < 16.0.7
    • —
    • 15.0.5
    • —
    • —
    • 15.3.6
    • 15.5.7
    • 15.1.9
    • 15.4.8
    • 15.2.6
    • 16.0.7

    Vendors and products

    Weakness classes (CWE)

    • CWE-502Deserialization of Untrusted Data

      Base

      The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

      Entry at MITRE CWE-502

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited
    ANSSI / CERT-FRLicence Ouverte 2.0, as of CERTFR-2025-ALE-014 – [MàJ] Vulnérabilité dans React Server Components (clôturée 2026-02-12) (opens in a new tab)cert.cyber.gouv.fractively exploited
    GitHubejpir/CVE-2025-55182-poc (opens in a new tab)github.comPoC (publicly reported)reported, not verified—
    PoC-in-GitHub (nomi-sec)CVE-2025-55182-React2Shell (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)ReactorWriteUp-HackTheBox (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)react2shell-scanner (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2025-55182 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)cve-2025-55182-ctf (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)React2Shell_CVE-2025-55182 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2025-55182-React2Shell (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)hackcar-writeup (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2025-55182 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2025-55182-poc (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2025-55182 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)React2shell-Research (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)React2Shell (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)Security_incident_report (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)cs50-cybersecurity (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)cve-2025-55182-react2shell-analysis (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2025-55182-Exploit (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)CVE-2025-55182-Advanced-React-Server-Components-RCE-Exploit (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)React2Shell-Exploit-CVE-2025-55182 (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)cve-2025-55182-react2shell_reproduction (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)Nextjs_Exploit_Tool (opens in a new tab)github.comPoC (publicly reported)reported, not verified
    PoC-in-GitHub (nomi-sec)reactorwatch-pentest (opens in a new tab)github.comPoC (publicly reported)reported, not verified

    References & sources

    • github.comfacebook/react/security/advisories/GHSA-fv66-9v8q-g76rweb
    • NVD (NIST)NVD: CVE-2025-55182advisory, pwn-watch
    • github.comfacebook/react/pull/35277web
    • github.comfacebook/react/commit/7dc903cd29dac55efb4424853fd0442fef3a8700web
    • github.comejpir/CVE-2025-55182-pocweb
    • github.comfacebook/reactpackage
    • github.comfacebook/react/releases/tag/v19.0.1web
    • github.comfacebook/react/releases/tag/v19.1.2web
    • github.comfacebook/react/releases/tag/v19.2.1web
    • news.ycombinator.comitem?id=46136026web, Issue tracking
    • react.devCritical Security Vulnerability in React Server Componentsweb, Patch, Vendor advisory, x_refsource_CONFIRM, pwn-watch
    • facebook.comsecurity/advisories/cve-2025-55182web, Vendor advisory, x_refsource_CONFIRM
    • openwall.comlists/oss-security/2025/12/03/4web, Mailing list, Patch, Third-party advisory
    • aws.amazon.comChina-nexus cyber threat groups rapidly exploit React2Shellmedia-coverage, Third-party advisory, pwn-watch
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2025-55182government-resource, US government resource
    • cert.atCERT.at: React2Shell - Angriffe gegen verwundbare Anwendungen auf von Basis React.JS und weiterer Frameworkscert-at
    • cert.cyber.gouv.frANSSI / CERT-FR: CERTFR-2025-ALE-014 – [MàJ] Vulnérabilité dans React Server Components (clôturée 2026-02-12)cert-fr
    • pwn.watchpwn.watch: React2Shell: CVSS 10 unauthenticated RCE in React Server Components and Next.jspwn-watch
    • cloud.google.comMultiple Threat Actors Exploit React2Shell (CVE-2025-55182)pwn-watch
    • unit42.paloaltonetworks.comExploitation of Critical Vulnerability in React Server Componentspwn-watch

    Changes to this CVE

    Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).

    1. NVD analysis modifiedNVD

    2. Record modifiedfb.com

      Show 6 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
      Referenceadded
      —
      https://www.facebook.com/security/advisories/cve-2025-55182
      Referenceremoved
      https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components
      —
      Referenceremoved
      https://www.facebook.com/security/advisories/cve-2025-55182
      —
      Reference typeremoved
      https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components Types: Patch, Vendor Advisory
      —
      Reference typeremoved
      https://www.facebook.com/security/advisories/cve-2025-55182 Types: Vendor Advisory
      —

      Source identifier: cve-assign@fb.com

    3. Record modifiedCISA ADP

      Show 9 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Weakness type (CWE)added
      —
      CWE-502
      Referenceadded
      —
      https://aws.amazon.com/blogs/security/china-nexus-cyber-threat-groups-rapidly-exploit-react2shell-vulnerability-cve-2025-55182/
      Referenceadded
      —
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-55182
      Referenceremoved
      https://aws.amazon.com/blogs/security/china-nexus-cyber-threat-groups-rapidly-exploit-react2shell-vulnerability-cve-2025-55182/
      —
      Referenceremoved
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-55182
      —
      Reference typeremoved
      https://aws.amazon.com/blogs/security/china-nexus-cyber-threat-groups-rapidly-exploit-react2shell-vulnerability-cve-2025-55182/ Types: Third Party Advisory
      —
      Reference typeremoved
      https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-55182 Types: US Government Resource
      —
      SSVC assessmentremoved
      {"id":"CVE-2025-55182","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2025-12-03T00:00:00+00:00"}
      —
      SSVC assessmentadded
      —
      {"id":"CVE-2025-55182","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-08-04T03:56:02.696515Z"}

      Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0

    4. Record modifiedCVE Program

      Show 6 original changes
      Individual changes of this event as published by NVD
      TypeActionBeforeAfter
      Referenceadded
      —
      http://www.openwall.com/lists/oss-security/2025/12/03/4
      Referenceadded
      —
      https://news.ycombinator.com/item?id=46136026
      Referenceremoved
      http://www.openwall.com/lists/oss-security/2025/12/03/4
      —
      Referenceremoved
      https://news.ycombinator.com/item?id=46136026
      —
      Reference typeremoved
      http://www.openwall.com/lists/oss-security/2025/12/03/4 Types: Mailing List, Patch, Third Party Advisory
      —
      Reference typeremoved
      https://news.ycombinator.com/item?id=46136026 Types: Issue Tracking
      —

      Source identifier: af854a3a-2127-422b-91ae-364da2661108

    One NVD translation into another language is hidden.

    Linked advisories

    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2025-55182
    <a href="https://intel.neosec.eu/en/cve/CVE-2025-55182"><img src="https://intel.neosec.eu/badge/cve/CVE-2025-55182.svg?lang=en" alt="CVE-2025-55182 – NEOSEC Intel" height="20"></a>