What is the CVSS score of EUVD-2026-26995?

EUVD-2026-26995 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of vm2 are affected by EUVD-2026-26995?

CVE-2026-26956 is a critical sandbox escape vulnerability in vm2 (Node.js sandboxing library) versions up to 3.10.4 that allows remote code execution on the host system without authentication.. A patch is available.

Is there a public PoC exploit available for EUVD-2026-26995?

Yes, a public proof-of-concept exploit is available for EUVD-2026-26995. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate EUVD-2026-26995?

Within 24 hours: Identify all systems running vm2 versions ≤3.10.4 using dependency scanning (npm audit, SBOM tools). Within 7 days: Upgrade all instances to vm2 version 3.10.5 or later and validate in staging environment. Within 30 days: Audit logs for suspicious code execution patterns in vm2 sandboxes and confirm full deployment across production, development, and CI/CD environments.

vm2 EUVD-2026-26995

| CVE-2026-26956 CRITICAL

Protection Mechanism Failure (CWE-693)

2026-05-04 GitHub_M

GHSA-ffh4-j6h5-pg66

RCE Node.js Vm2 Patriksimek

9.8

CVSS 3.1 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Red Hat

9.8 HIGH

qualitative

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Source Code Evidence Fetched

May 04, 2026 - 17:46 vuln.today

Analysis Generated

May 04, 2026 - 17:46 vuln.today

EUVD ID Assigned

May 04, 2026 - 17:15 euvd

EUVD-2026-26995

Analysis Generated

May 04, 2026 - 17:15 vuln.today

CVE Published

May 04, 2026 - 16:37 nvd

CRITICAL 9.8

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

11 npm packages depend on vm2 (1 direct, 10 indirect)

Ecosystem-wide dependent count for version 3.10.5.

DescriptionCVE.org

vm2 is an open source vm/sandbox for Node.js. In version 3.10.4, vm2 is vulnerable to full sandbox escape with arbitrary code execution. Attacker code inside VM.run() obtains host process object and runs host commands with zero host cooperation. This issue has been patched in version 3.10.5.

AnalysisAI

Full sandbox escape with arbitrary code execution allows remote attackers to break out of vm2's Node.js sandbox environment (version 3.10.4) and execute commands on the host system. Attacker-controlled code running inside VM.run() can obtain the host process object and execute arbitrary host commands without any cooperation from the host application. EPSS data not available, but this represents complete failure of the sandbox security boundary. Patch released in version 3.10.5 addresses eleven distinct escape vectors including Function constructor leakage, proxy unwrapping, util.inspect exposure, and WebAssembly exception handling.

Technical ContextAI

vm2 (cpe:2.3:a:patriksimek:vm2:*:*:*:*:*:*:*:*) is a Node.js library designed to provide sandboxed JavaScript execution environments. The vulnerability stems from CWE-693 (Protection Mechanism Failure) - specifically, multiple failures in the isolation boundary between guest and host JavaScript contexts. Version 3.10.4 contains at least eleven distinct escape paths discovered during remediation, including: Function constructor access via getOwnPropertyDescriptor, proxy handler exploitation, exposure of internal bridge methods (doPreventExtensions, getFactory) through util.inspect, nested property descriptor manipulation, SuppressedError object leakage, direct handler.get() calls, and WebAssembly.JSTag exception handling in Node 25. The sandbox relied on prototype manipulation and context isolation that could be bypassed through creative use of JavaScript reflection APIs and Node.js internals.

RemediationAI

Upgrade immediately to vm2 version 3.10.5 or later (https://github.com/patriksimek/vm2/releases/tag/v3.10.5). The patched version implements comprehensive fixes for eleven distinct sandbox escape vectors including Function constructor blocking across all access paths, proxy unwrapping prevention, util.inspect internal method sanitization, SuppressedError sub-error sanitization, and WebAssembly.JSTag blocking for Node 25 environments. No workarounds exist for version 3.10.4 - the sandbox security boundary is fundamentally broken. If immediate upgrade is impossible, disable all vm2-based code execution features until patching is complete. For defense in depth post-patch, run Node.js processes using vm2 with OS-level sandboxing (containers, seccomp, AppArmor) and minimal filesystem/network privileges, though this does not address the application-level escape. Refer to GHSA-ffh4-j6h5-pg66 for complete advisory details.