CVE-2025-55182 Elastic Security · Elastic

Detect CVE-2025-55182 — Meta React Server Components Remote Code Execution in Elastic Security

Detects exploitation of CVE-2025-55182, a critical remote code execution vulnerability in Meta React Server Components. This vulnerability allows attackers to achieve server-side code execution by abusing the React Server Components protocol, potentially leading to full server compromise. The vulnerability is actively exploited in the wild (CISA KEV).

MITRE ATT&CK

Tactic
Initial Access Execution Persistence Impact

Elastic Detection Query

Elastic Security (Elastic)
eql
sequence by host.hostname with maxspan=2m
  [process where event.type == "start"
   and process.name in~ ("node", "node.exe", "next")
   and process.args : ("*child_process*", "*execSync*", "*spawnSync*", "*eval*", "*vm.runIn*")]
  [any where event.category in ("file", "network", "process")
   and (
     (event.category == "file" and file.path : ("/tmp/*", "/var/tmp/*", "C:\\Windows\\Temp\\*") and file.extension in ("sh", "py", "elf", "exe", "pl"))
     or (event.category == "network" and destination.port in (4444, 1337, 9001) and network.direction == "egress")
     or (event.category == "process" and process.parent.name in~ ("node", "node.exe") and process.name in ("sh", "bash", "cmd.exe", "powershell.exe", "python3", "python"))
   )
  ]
critical severity high confidence

EQL sequence rule that correlates a Node.js process with suspicious argument patterns (CVE-2025-55182 exploit vectors) followed within 2 minutes by file writes to temp directories, outbound connections to high-risk ports, or shell spawning — indicating successful RCE.

Data Sources

Elastic SecurityEndpoint Agent (Elastic)

Required Tables

logs-endpoint.events.process-*logs-endpoint.events.file-*logs-endpoint.events.network-*

False Positives & Tuning

  • Build toolchains using Node.js to invoke shell scripts as part of webpack or Vite pipelines
  • Container orchestration systems that spawn shells from Node.js management daemons
  • Penetration testing activities against non-production React Server Component deployments
  • Misconfigured development environments exposing Node.js debug ports

Other platforms for CVE-2025-55182


Testing Methodology

Validate this detection against 4 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.

  1. Test 1CVE-2025-55182 RSC Protocol RCE Simulation — Command Execution via child_process

    Expected signal: EDR telemetry: ProcessCreate event with parent=node, child=sh or node with args containing execSync. Audit logs: execve syscall for 'id', 'whoami', 'hostname' with parent PID matching the node process.

  2. Test 2CVE-2025-55182 RSC Exploitation — Reverse Shell Payload Drop to /tmp

    Expected signal: File creation event in /tmp with .sh extension, owned by node process user, with executable permissions set. EDR FileCreated event with FolderPath=/tmp and FileName=rsc_test_shell.sh.

  3. Test 3CVE-2025-55182 RSC Post-Exploitation — Dynamic Code Evaluation Abuse

    Expected signal: Process event showing node.exe/node with args containing vm.runInNewContext. If eval succeeds, subsequent execve events for 'id' binary with node as ancestor process.

  4. Test 4CVE-2025-55182 RSC Network C2 Beacon Simulation

    Expected signal: Network connection event from node process to 127.0.0.1:4444 (substitute real C2 IP in production test). EDR NetworkConnectionFound or equivalent with InitiatingProcessFileName=node and RemotePort=4444.

Unlock Pro Content

Get the full detection package for CVE-2025-55182 including response playbook, investigation guide, and atomic red team tests.

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections