dbcve.org
CWE-913Weakness · CWE-913

CVE-2026-47137

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, the fix for GHSA-8hg8-63c5-gwmx (CVE-2023-37903) introduced a check in nodevm.js line 263 that blocks the combination nesting: true + require: false. However, the check uses strict equality (options.require === false), which is trivially bypassed by omitting the require option entirely. When require is not specified, options.require is undefined, not false. The strict equality check fails, so the security guard is skipped. Immediately after (line 280), the destructuring default require: requireOpts = false assigns requireOpts = false, producing the exact configuration the patch was designed to prevent. 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 versions before 3.11.4 contain a security bypass in nodevm.js where a strict equality check (options.require === false) intended to block the dangerous nesting:true + require:false configuration can be trivially bypassed by omitting the require option entirely. When require is not specified, options.require is undefined, causing the equality check to fail, after which a destructuring default assigns requireOpts = false, creating the exact unsafe configuration the original patch was meant to prevent.

MitigationUpdate vm2 to version 3.11.4 or later to apply the patched strict equality logic.

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. Check if vm2 is installed
    Look for vm2 in your project's dependencies: inspect package.json for 'vm2' under dependencies/devDependencies, or run 'npm list vm2' to see if it's installed as a dependency
    Affected if vm2 is not present in the project at all, then you are not affected by this vulnerability
  2. Determine installed vm2 version
    Run 'npm list vm2' or check the version field in node_modules/vm2/package.json. Compare the version to the affected range: versions before 3.11.4 are vulnerable
    Affected if The installed version is lower than 3.11.4 (e.g., 3.11.3, 3.10.0, etc.)
  3. Identify use of nodevm.js
    Search your codebase for imports or requires of 'vm2/nodevm' or 'vm2', as nodevm.js is the specific file containing the vulnerable code. Check where VM is being instantiated from vm2
    Affected if Your code uses nodevm (the NodeVM class) from vm2 rather than other vm2 modules like vm1 or the main VM
  4. Inspect VM configuration for nesting:true
    Review the options object passed when creating a NodeVM instance. Look for nesting:true being set in the configuration object
    Affected if The NodeVM is configured with nesting:true enabled
  5. Check require option configuration
    Examine whether the 'require' option is explicitly set to false, or whether it is omitted entirely from the options object. Both scenarios trigger the bypass in versions before 3.11.4
    Affected if The require option is either set to false or is not specified in the options (omitted/undefined), combined with nesting:true

You are affected if vm2 version is below 3.11.4 and your code uses NodeVM with nesting:true and either require:false or no require option specified.

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
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Update vm2 to version 3.11.4 or later to apply the patched strict equality logic.

Recommended fix High confidence

3.11.4

  1. 1. Identify the project(s) that depend on vm2 by checking package.json for 'vm2' in dependencies or devDependencies
  2. 2. Run 'npm list vm2' to verify the current installed version of vm2
  3. 3. Update the vm2 dependency to version 3.11.4 or later using 'npm install [email protected]' or update via package.json
  4. 4. Run 'npm audit' or 'npm list vm2' to confirm the new version is installed
  5. 5. Test the application to ensure the sandbox functionality still works as expected
  6. 6. Rebuild and redeploy the application

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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