CVE-2026-47140
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. Prior to version 3.11.4, NodeVM blocks several dangerous Node.js builtins such as module, worker_threads, cluster, vm, repl, and inspector. However, the denylist misses process and inspector/promises. Both can be used from sandboxed code to reach host-side execution primitives. This allows sandboxed code to bypass the intended builtin restrictions and execute code in the host process. 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 confidencevm2 sandbox's NodeVM feature uses a denylist to block dangerous Node.js builtins (module, worker_threads, cluster, vm, repl, inspector), but misses `process` and `inspector/promises` from the blocklist. Attackers can use these unblocked globals to escape the sandbox and execute arbitrary code in the host Node.js process, completely bypassing intended isolation.
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 checksWork through these to decide whether this CVE applies to you.
-
Locate vm2 in your project dependenciesSearch for vm2 in package.json files or list it via 'npm list vm2' or 'yarn list vm2' in your project directoryAffected if vm2 is listed as a dependency
-
Determine the installed vm2 versionRun 'npm list vm2' or check the version field in node_modules/vm2/package.jsonAffected if vm2 version is present but lower than 3.11.4
-
Identify if NodeVM feature is being usedSearch your codebase for 'NodeVM' or 'new NodeVM' instantiation patterns in your JavaScript/TypeScript source filesAffected if Code creates a NodeVM instance for sandboxing user-provided code
-
Verify if process global is accessible within sandboxed codeExecute a test script that runs inside NodeVM and attempts to access 'process' (e.g., try 'process.exit' or 'process.cwd')Affected if The process global is accessible and not undefined inside the sandbox context
-
Verify if inspector/promises is accessible within sandboxed codeExecute a test script that runs inside NodeVM and attempts to require('inspector/promises')Affected if The inspector/promises module can be required and used inside the sandbox context
Your environment is affected if vm2 version is below 3.11.4, you use the NodeVM feature, and either the process global or inspector/promises module is accessible from within the sandboxed code.
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 · scopedUpgrade vm2 to version 3.11.4 or later to include process and inspector/promises in the builtin denylist. Review any code that depends on vm2's sandboxing to confirm no unauthorized code execution occurred during the vulnerable period.
vm2 version 3.11.4 or later
- Check the current vm2 version in use (e.g., via 'npm list vm2' or inspect package.json)
- Upgrade vm2 to version 3.11.4 or later using 'npm install [email protected]' or 'npm install vm2@latest'
- After upgrading, verify the sandbox properly blocks the process and inspector/promises built-ins
- Test your sandboxed code to ensure functionality remains intact
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47140 — 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-47140 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