dbcve.org
CWE-913Weakness · CWE-913

CVE-2026-47208

CRITICAL · 10.0 CVSS v3.1 Published 2026-06-12
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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.4, VM2 suffers from a sandbox breakout vulnerability. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. This issue has been patched in version 3.11.4.

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 is a Node.js sandbox library. Prior to version 3.11.4, the sandbox contains a vulnerability allowing attackers to break out of the isolation and execute arbitrary commands on the host system with the privileges of the Node.js process.

MitigationUpgrade vm2 to version 3.11.4 or later to apply the patch. Review existing code using vm2 to verify the sandbox behavior remains correct after the update.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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. Locate vm2 in project dependencies
    Search your project for vm2 in package.json, package-lock.json, or yarn.lock files. Also check node_modules/vm2/package.json if node_modules exists.
    Affected if vm2 is listed as a dependency in any of these files
  2. Identify installed vm2 version
    Run 'npm list vm2' or 'yarn list vm2' in your project directory, or directly read the version field from node_modules/vm2/package.json
    Affected if The installed version is lower than 3.11.4 (e.g., 3.11.3, 3.10.0, etc.)
  3. Check if vm2 is actually used in code
    Search your codebase for require('vm2'), import * as vm2, or new vm2.Sandbox() patterns using grep or your IDE search
    Affected if Code imports or instantiates vm2 to run untrusted or external code within a sandbox
  4. Verify sandbox handles untrusted input
    Review the code paths using vm2 to determine whether untrusted user input, external data, or third-party code is passed to the sandbox
    Affected if vm2 processes untrusted input without additional containment beyond the vm2 sandbox itself

Your environment is affected if vm2 version 3.11.4 or later is not installed AND your code actively uses vm2 to run untrusted or external code.

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.

From vendor data
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade vm2 to version 3.11.4 or later to apply the patch. Review existing code using vm2 to verify the sandbox behavior remains correct after the update.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47208 — 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-47208 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