CVE-2025-55182 Splunk · SPL

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

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

SPL Detection Query

Splunk (SPL)
spl
index=* sourcetype IN ("WinEventLog:Security", "linux_secure", "osquery:results", "stream:http")
| eval is_node = if(match(process, "(?i)(node|next)"), 1, 0)
| eval is_suspicious_cmd = if(match(cmdline, "(?i)(child_process|execSync|spawnSync|eval|Function\\(|vm\.runInNewContext|os\.system|subprocess|shell_exec)"), 1, 0)
| eval is_suspicious_file = if(match(file_path, "(?i)(\/tmp\/|\/var\/tmp\/|\\\\Temp\\\\).*\.(sh|py|pl|rb|elf|exe)$"), 1, 0)
| eval is_rsc_rce = if(is_node=1 AND (is_suspicious_cmd=1 OR is_suspicious_file=1), 1, 0)
| where is_rsc_rce=1
| eval exploit_stage = case(
    is_suspicious_cmd=1 AND match(cmdline, "(?i)(child_process|exec)"), "InitialCodeExecution",
    is_suspicious_cmd=1 AND match(cmdline, "(?i)(eval|Function)"), "DynamicEvalAbuse",
    is_suspicious_file=1, "PayloadDrop",
    true(), "Unknown"
)
| table _time, host, user, process, cmdline, file_path, exploit_stage, src_ip
| sort -_time
critical severity medium confidence

Searches for Node.js/Next.js processes executing suspicious commands or dropping files in temp directories, which are indicators of CVE-2025-55182 post-exploitation activity on React Server Components hosts.

Data Sources

Splunk Enterprise SecurityWindows Event LogsLinux Secure Logsosquery

Required Sourcetypes

WinEventLog:Securitylinux_secureosquery:results

False Positives & Tuning

  • CI/CD pipelines that use Node.js to orchestrate build scripts involving shell commands
  • Legitimate Next.js applications using dynamic imports or eval in controlled contexts
  • Security tooling that instruments Node.js processes for dynamic analysis
  • Development hot-reload mechanisms that write temporary files to /tmp

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