EUVD-2026-81588
GHSA-m7cq-7f2q-f9fh
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
PR:L because running in the sandbox is a granted privilege; AC:H for the multi-step readonly/double-prefix bypass plus required on-disk native lib; S:C and C/I/A:H for full host escape.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
Lifecycle Timeline
4DescriptionCVE.org
vm2 versions 3.11.3 through 3.11.6 expose Node.js's host node:sqlite module to code running in NodeVM when that builtin is permitted, either explicitly or through builtin: ['*']. The module is wrapped with vm.readonly(), which prevents property assignment but leaves host-authority callables reachable; in addition, the resolver treats any request starting with 'node:' as a core-module request and the runtime strips only one 'node:' prefix, so a sandbox request for 'node:node:sqlite' resolves to the configured node:sqlite entry. Sandboxed code can therefore create an in-memory DatabaseSync with extension loading enabled and call DatabaseSync.loadExtension() on a native library bundled in the untrusted plugin package (path derived from __dirname). SQLite loads the library into the Node.js host process and invokes its native entry point, giving the sandboxed plugin arbitrary native code execution outside the sandbox with the host process's privileges. The issue is fixed in vm2 3.11.7.
Articles & Coverage 1
AnalysisAI
Native code execution outside the sandbox affects vm2 versions 3.11.3 through 3.11.6 when the host node:sqlite builtin is exposed to a NodeVM sandbox - either explicitly or through the wildcard builtin: ['*'] - which is not a default configuration. Sandboxed plugin code can create an in-memory DatabaseSync with extension loading turned on, resolve an attacker-supplied native library via a __dirname-derived path, and call loadExtension(), causing SQLite to load that library into the Node.js host process and execute its native entry point with host privileges; the vm.readonly() wrapper prevents property assignment but leaves host-authority callables reachable, and a 'node:node:sqlite' double-prefix quirk in the resolver/prefix-stripping logic lets the sandbox reach the configured builtin. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Requires all of: (1) the application runs untrusted/attacker-supplied code in vm2's NodeVM (the vm2 threat model); (2) the host node:sqlite builtin is exposed to the sandbox, either listed explicitly or via the wildcard builtin: ['*'] - this is not a default; (3) SQLite extension loading is enabled on the DatabaseSync instance; and (4) an attacker-controlled native library (.so/.dll) is present on disk within the plugin package, reachable via a __dirname-derived path. … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | This is a genuine high-severity issue within its threat model but its real-world priority is strongly gated by configuration. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | Full exploit scenario with step-by-step reproduction available after sign-in. |
| Remediation | Vendor-released patch: upgrade to vm2 3.11.7, which fixes the issue (advisory: https://github.com/patriksimek/vm2/security/advisories/GHSA-6w8r-xxw2-g3hx). … Detailed patch versions, workarounds, and compensating controls in full report. |
Recommended ActionAI
Within 24 hours, inventory every Node.js service using vm2 and confirm whether any instance runs version 3.11.3 through 3.11.6; for those, immediately inspect sandbox configuration and remove 'node:sqlite' from any explicit builtin allowlist and eliminate the wildcard 'builtin: ["*"]' setting, and where untrusted plugins are processed, disable SQLite extension loading and drop plugin execution privileges to the minimum. …
Sign in for detailed remediation steps and compensating controls.
Threat intelligence, references, and detailed analysis are available after sign-in.
A vulnerability in the NuPoint Unified Messaging (NPM) component of Mitel MiCollab through 9.8 SP1 FP2 (9.8.1.201) could
FortiOS and FortiProxy contain an authentication bypass via the Node.js websocket module allowing unauthenticated remote
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Eval injection vulnerability in the internals.batch function in lib/batch.js in the bassmaster plugin before 1.5.2 for t
Flowise version 3.0.5 contains a remote code execution vulnerability in the CustomMCP node. The mcpServerConfig paramete
Node.js 8.5.0 before 8.6.0 allows remote attackers to access unintended files, because a change to ".." handling was inc
An issue was discovered in the node-serialize package 0.0.4 for Node.js. Rated critical severity (CVSS 9.8), this vulner
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
Directory traversal vulnerability in the st module before 0.2.5 for Node.js allows remote attackers to read arbitrary fi
Multiple SQL injection vulnerabilities in the Manage Accounts page in the AccountManagement.asmx service in the Solarwin
The JS-YAML module before 2.0.5 for Node.js parses input without properly considering the unsafe !!js/function tag, whic
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
Same weakness CWE-693 – Protection Mechanism Failure
View allShare
External POC / Exploit Code
Leaving vuln.today