CVE-2026-47140 Sumo Logic CSE · Sumo

Detect CVE-2026-47140 — vm2 Builtin Denylist Bypass via process/inspector Leads to Host RCE in Sumo Logic CSE

Detects exploitation of CVE-2026-47140, a critical sandbox escape in the npm vm2 package (versions <= 3.11.3). Attackers bypass the builtin module denylist using process and inspector/promises references to execute arbitrary code on the host Node.js process. CVSS 10.0. PoC is publicly available.

MITRE ATT&CK

Tactic
Execution Privilege Escalation Lateral Movement

Sumo Detection Query

Sumo Logic CSE (Sumo)
sql
_sourceCategory=endpoint/windows OR _sourceCategory=endpoint/linux
| where _raw matches /node(\.exe)?/
| parse regex "(?<cmdline>(?:CommandLine|command_line|cmd)\s*[=:]\s*\S+)" nodrop
| where cmdline matches /vm2|NodeVM|new\s+VM/i
| lookup type=geo destinationip from shared/CIDRlookup on cidr return isPrivate
| where !(isPrivate)
| stats count as suspicious_connections, values(destinationip) as remote_ips, first(_messagetime) as first_seen, last(_messagetime) as last_seen by host, user, cmdline
| where suspicious_connections > 0
| sort by suspicious_connections desc
| fields host, user, cmdline, suspicious_connections, remote_ips, first_seen, last_seen
critical severity medium confidence

Sumo Logic query detecting Node.js processes with vm2 references making outbound connections to public IP addresses, which may indicate exploitation of CVE-2026-47140.

Data Sources

Sumo Logic Installed Collector (Windows/Linux)Sysmon via Sumo LogicCloud SIEM Enterprise

Required Tables

endpoint/windowsendpoint/linux

False Positives & Tuning

  • Legitimate Node.js microservices using vm2 for sandboxing with required external API access
  • npm package testing pipelines that download dependencies while running vm2 tests
  • Security scanning tools using vm2 for dynamic analysis with outbound reporting
  • Multi-tenant SaaS backends that use vm2 for user code isolation with authorized egress

Other platforms for CVE-2026-47140


Testing Methodology

Validate this detection against 3 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 1vm2 Sandbox Escape via inspector/promises — Host Code Execution

    Expected signal: Sysmon/auditd will log: (1) node process launch with vm2 in path or arguments, (2) file creation event at /tmp/vm2_escape_poc.txt by the node process, (3) a child process or execSync call spawning sh/bash from within node

  2. Test 2vm2 Escape with Outbound Network Callback (Simulated C2 Beacon)

    Expected signal: Network flow logs will show an outbound HTTP connection to example.com originating from the node process PID. EDR should capture the network connect event and correlate it to the parent node process with vm2 in its command line.

  3. Test 3vm2 Escape via process.binding — Enumerate Host Environment Secrets

    Expected signal: File write event at /tmp/vm2_env_harvest.json attributed to node process. Process event showing node with potential vm2-related arguments. EDR may also capture the internal environment variable enumeration if it hooks process.env access.

Unlock Pro Content

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

Response PlaybookInvestigation GuideHunting QueriesAtomic Red Team TestsTuning Guidance

Related Detections