CVE-2026-26956
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 version 3.10.4, vm2 is vulnerable to full sandbox escape with arbitrary code execution. Attacker code inside VM.run() obtains host process object and runs host commands with zero host cooperation. This issue has been patched in version 3.10.5.
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 version 3.9.4 contains a critical sandbox escape vulnerability where code executing inside VM.run() can obtain a reference to the host process object and execute arbitrary commands on the host system with full privileges, completely bypassing sandbox isolation.
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.5CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 vm2 installationSearch for vm2 in your project's dependencies: check package.json for 'vm2' in dependencies/devDependencies, or run 'npm list vm2' in your project root to list the installed package.Affected if vm2 is present in your project dependencies
-
Determine installed vm2 versionRun 'npm list vm2' or inspect the version field in node_modules/vm2/package.json to obtain the exact installed version number.Affected if The installed version is 3.10.4 or any version lower than 3.10.5
-
Locate VM.run() usageSearch your codebase for calls to 'VM.run()' or 'new VM()' patterns, typically in files that import or require vm2. Use grep or IDE search for 'vm2' and 'VM.run'.Affected if Your code executes VM.run() to run JavaScript code within the vm2 sandbox
-
Assess untrusted code contextReview the code passed to VM.run() to determine whether it originates from user input, external APIs, or other untrusted sources rather than purely internal trusted code.Affected if VM.run() processes code from untrusted or external sources
You are affected if vm2 version < 3.10.5 is installed AND your application uses VM.run() to execute untrusted JavaScript code within the sandbox.
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.5
Upgrade vm2 to version 3.9.5 or later to apply the patch. Audit all deployments using vm2 to confirm the vulnerable version is not in production.
vm2 version 3.10.5
- Check current vm2 version in your project by running `npm list vm2` or reviewing package.json
- Update package.json to specify vm2 version 3.10.5 or higher: `npm install vm2@^3.10.5 --save`
- Run `npm install` or `npm update` to install the patched version
- Verify the correct version is installed by running `npm list vm2`
- Test your application to ensure the sandbox functionality works correctly after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-26956 — 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-26956 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