What is the CVSS score of CVE-2026-45411?

CVE-2026-45411 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%.

Is there a public PoC exploit available for CVE-2026-45411?

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

How to fix or mitigate CVE-2026-45411?

Within 24 hours: Inventory all applications and dependencies using vm2 (npm audit, SCA tools, package.json review across development and production environments). Within 7 days: Upgrade all instances to vm2 version 3.11.3 or later and validate in staging environments. Within 30 days: Confirm all production systems are running 3.11.3+, implement WAF rules to block suspicious vm2 requests where applicable, and enable audit logging for code execution endpoints.

vm2 CVE-2026-45411

Q: Which versions of vm2 are affected by CVE-2026-45411?

vm2 versions prior to 3.11.3 contain a critical sandbox escape vulnerability enabling remote code execution on the host Node.js process; publicly available exploit code exists for this vulnerability.. A patch is available.

EUVD-2026-30086 CRITICAL

Exposure of Resource to Wrong Sphere (CWE-668)

2026-05-13 GitHub_M

GHSA-248r-7h7q-cr24

Information Disclosure Node.js Vm2

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

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

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

Jun 08, 2026 - 08:26 vuln.today

Analysis Generated

Jun 08, 2026 - 08:26 vuln.today

Patch available

May 13, 2026 - 19:17 EUVD

Blast Radius

ecosystem impact

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

16 npm packages depend on vm2 (5 direct, 11 indirect)

Ecosystem-wide dependent count for version 3.11.3.

DescriptionCVE.org

vm2 is an open source vm/sandbox for Node.js. Prior to 3.11.3, it is possible to catch a host exception using the yield* expression inside an async generator. When the generator is closed using the return function, the value is awaited on and exceptions thrown in the then call will be caught by the runtime and passed to the yield* iterator as the next value. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. This vulnerability is fixed in 3.11.3.

AnalysisAI

Sandbox escape in vm2 (patriksimek/vm2) versions prior to 3.11.3 enables remote code execution on the host Node.js process by abusing async generator yield* semantics to smuggle a host-realm exception into sandbox code, where the attacker pivots through .constructor.constructor to reach process and child_process.execSync. The flaw is exploitable by any attacker who can run JavaScript inside the sandbox, has publicly available exploit code, and carries SSVC technical impact 'total' with automatable=yes, though EPSS remains low at 0.05% (17th percentile) and the CVE is not listed in CISA KEV.

Technical ContextAI

vm2 is a widely-used Node.js library that purports to provide a secure JavaScript sandbox by isolating untrusted code from the host realm via a transformer, a proxy bridge, and overrides of Promise.prototype.then and catch handlers. The root cause is CWE-668 (Exposure of Resource to Wrong Sphere): when an async generator delegates via yield* to an inner iterator lacking a return method, calling i.return(thenable) causes V8's internal PromiseResolveThenableJob to invoke thenable.then in C++ and catch any synchronous throw without going through a JavaScript try/catch or the user-visible Promise.prototype.then. Both of vm2's existing chokepoints - the transformer's catch-clause instrumentation and the globalPromise.prototype.then rejection sanitiser - are bypassed, so a host-realm RangeError triggered by deep recursion inside the V8 resolver job is surfaced to sandbox code unwrapped, exposing the host Function constructor and from there the Node.js process global. CPE coverage is cpe:2.3:a:patriksimek:vm2:* with all versions <= 3.11.2 affected.

RemediationAI

Vendor-released patch: vm2 3.11.3 - upgrade immediately via npm install vm2@3.11.3 or equivalent lockfile update, per the GHSA-248r-7h7q-cr24 advisory (https://github.com/patriksimek/vm2/security/advisories/GHSA-248r-7h7q-cr24) and the fix commit 093494c0c3ef2390d2e56909f9d56e290e6f18b0. Because vm2 has a long history of similar sandbox escapes and is no longer actively maintained as a security boundary, the strongly recommended remediation is to migrate away from vm2 entirely to isolated-vm or to OS-level isolation (separate process, container, V8 isolate, or WASM runtime) for evaluating untrusted code; this is the only durable mitigation against the broader class of escapes and is the path the upstream maintainer has publicly recommended. If immediate migration is not feasible and 3.11.3 cannot be applied right away, do not accept attacker-controlled JavaScript into vm2 - gate the sandbox behind authentication, refuse code submission from untrusted callers, drop privileges on the Node.js process (non-root user, seccomp, read-only filesystem) so a successful escape lands in a constrained environment, and monitor for unexpected child_process spawns from the Node host; the trade-off is that all of these are defense-in-depth and do not actually close the bug.