AIKIDO-2026-788042
vm2 is vulnerable to Sandbox Escape
99
Critical Risk
This Affects:
vm2TL;DR
When the crypto builtin is exposed through the read-only proxy bridge, calls are forwarded to the host implementation with arguments converted back to host values. crypto.setEngine() accepts a filesystem path and instructs OpenSSL to dynamically load that native library. Sandboxed code bundles a malicious native library and calls setEngine() pointing to it, and the operating system loader runs the library's constructors in the host process, yielding native code execution. The fix prevents the sandbox from reaching the dynamic engine-loading path.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and you expose the crypto builtin to the sandbox.
Background info
vm2 is vulnerable to Sandbox Escape in versions 3.11.3 - 3.11.6.
How to fix this
Upgrade the vm2 library to the patch version.
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant