How widely exploitable is this vulnerability?

Exploitability depends on how vm2 is integrated. If remote users or external systems can provide JavaScript or configuration that vm2 executes, exploitation can be fully remote. In closed systems where only trusted administrators can supply code, the risk is lower but not negligible.

Does an attacker need authenticated access to exploit this?

Not necessarily. The key requirement is the ability to influence code executed inside vm2. In some deployments this may require authenticated access, while in others—such as public code runners or multi-tenant platforms—untrusted users may be able to submit code directly.

What is the safest general fix pattern?

The safest approach is to combine library-level fixes with architectural hardening: apply the patched vm2 version, isolate sandboxed execution in separate low-privilege processes or containers, and avoid granting the Node.js runtime unneeded access to the filesystem, shell, or sensitive credentials.

Severity:

CRITICAL RISK

(9.8)

Sandbox Escape via Code Injection (CWE-94) in vm2 Node.js Sandbox

CVE-2026-24120

Published:

May 4, 2026

Status:

Received

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Sandbox Escape / Code Injection

CWE:

CWE-94;CWE-693

Impact:

Remote Code Execution on Host from Sandbox Context

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Sandbox Escape / Code Injection

CWE:

CWE-94;CWE-693

Impact:

Remote Code Execution on Host from Sandbox Context

Severity:

CRITICAL RISK

(9.8)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Sandbox Escape via Code Injection (CWE-94) in vm2 Node.js Sandbox

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal