CVE-2026-22709
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedvm2 is an open source vm/sandbox for Node.js. In vm2 prior to version 3.10.2, `Promise.prototype.then` `Promise.prototype.catch` callback sanitization can be bypassed. This allows attackers to escape the sandbox and run arbitrary 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. Version 3.10.2 fixes the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencevm2 sandbox for Node.js fails to sanitize callbacks on globalPromise.prototype.then and globalPromise.prototype.catch, while localPromise.prototype.then IS sanitized. Since async functions return globalPromise objects, attackers can bypass the sandbox isolation and execute arbitrary code outside the sandboxed environment.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.10.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if vm2 is installedRun 'npm list vm2' in your project directory or inspect node_modules/vm2/package.jsonAffected if vm2 is listed as a dependency or vm2 directory exists in node_modules
-
Determine the installed vm2 versionRun 'npm list vm2' or read the version field from node_modules/vm2/package.jsonAffected if The version number is less than 3.10.2 (e.g., 3.10.1, 3.9.x, etc.)
-
Check for code using the vm2 sandbox with async functionsSearch your codebase for patterns like 'new VM({...})' or 'vm2' combined with 'async' or 'await' keywords, or where Promise-returning code is passed to the sandboxAffected if Your code passes async functions or promises to the vm2 sandbox (e.g., vm.runInSandbox(async () => {...}) or similar patterns)
-
Inspect sandbox usage with promise-based operationsReview any code paths where .then() or .catch() are called on promises that originated from or passed through the vm2 sandboxAffected if Your application calls .then() or .catch() on promises returned from or processed through vm2 sandboxed code
You are affected if vm2 version is below 3.10.2 AND your code passes async functions or promises through the vm2 sandbox to have their .then/.catch methods accessed.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped3.10.2
Upgrade vm2 to version 3.10.2 or later. Audit all code paths that use the sandbox to verify no exploitation occurred prior to patching.
vm2 version 3.10.2 or latest
- Check the current vm2 version in your project by running: npm list vm2 or yarn list vm2
- Update vm2 to version 3.10.2 or later by running: npm install [email protected] (or npm install vm2@latest for the most recent version)
- Verify the installation was successful: npm list vm2
- Rebuild and redeploy your application to ensure the new vm2 version is used
- Test that the sandbox functionality still works as expected after the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing4.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-22709 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-22709 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data