dbcve.org
Vm2Application · Vm2 Project

CVE-2026-26332

CRITICAL · 10.0 CVSS v3.1 Published 2026-05-04
Fix available
A fix is available. Upgrade to 3.11.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
vm2 is an open source vm/sandbox for Node.js. Prior to version 3.11.0, SuppressedError allows attackers to escape the sandbox and run arbitrary code. This issue has been patched in version 3.11.0.

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 confidence

vm2 versions before 3.11.0 contain a SuppressedError vulnerability that allows attackers to escape the sandbox isolation and execute arbitrary code on the host system. This is a critical sandbox escape flaw enabling full code execution outside the intended isolation boundary.

MitigationUpdate vm2 to version 3.11.0 or later to patch the SuppressedError sandbox escape vulnerability. Given the CVSS 10 severity and arbitrary code execution capability, prioritize this update immediately and audit systems for potential prior exploitation.

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
Vm2Application
Affected:< 3.11.0

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Find vm2 in your project dependencies
    Check your package.json for 'vm2' in dependencies or devDependencies, or run 'npm list vm2' to see if it's installed as a transitive dependency
    Affected if vm2 appears in your dependency tree
  2. Identify the installed vm2 version
    Run 'npm list vm2' or check the version in node_modules/vm2/package.json under the 'version' field
    Affected if The version is lower than 3.11.0 (e.g., 3.10.x, 3.9.x, etc.)
  3. Determine if your code uses the sandbox with SuppressedError
    Search your codebase for patterns like 'new vm2.VM()', 'new vm2.NodeVM()', or 'vm2' imports that create sandboxed environments, and check if SuppressedError from Node.js is being thrown within the sandbox
    Affected if You create vm2 sandbox instances and any untrusted code could trigger error handling paths that involve SuppressedError
  4. Verify Node.js version in use
    Run 'node --version' to check your Node.js version. Some sandbox escapes may behave differently across Node.js versions
    Affected if Running any Node.js version with vm2 < 3.11.0
  5. Check for any vulnerable code paths
    Review any code that uses vm2 to run untrusted or user-supplied code, particularly where errors might be thrown and caught within the sandbox context
    Affected if You execute untrusted code within vm2 sandboxes and are on a version below 3.11.0

You are affected if vm2 version less than 3.11.0 is installed and you use it to run untrusted code in sandboxed environments.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.11.0 or later
Fixed in 3.11.0
Interim mitigation

Update vm2 to version 3.11.0 or later to patch the SuppressedError sandbox escape vulnerability. Given the CVSS 10 severity and arbitrary code execution capability, prioritize this update immediately and audit systems for potential prior exploitation.

Recommended fix High confidence

vm2 version 3.11.0

  1. Check package.json or package-lock.json to identify vm2 usage and current version
  2. Run 'npm install [email protected]' or 'npm update vm2' to upgrade to the fixed version
  3. Verify the upgrade was successful by checking 'npm list vm2'
  4. Test the application to ensure sandbox functionality works as expected after the upgrade
  5. Redeploy the application if necessary

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Vm2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-26332 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-26332 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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