GHSA-6jgm-4w45-vh8j: Duplicate Advisory Vm2 Crypto Builtin Loads Attacker Vulnerability
CRITICALGHSA-6jgm-4w45-vh8j is a CRITICAL (CVSS 9.9) vm2 crypto builtin loads attacker vulnerability (CWE-114: Process Control) affecting Duplicate Advisory libraries in the npm ecosystem. The issue involves vm2 crypto builtin loads attacker native code through setengine. Remediation is available in the latest vendor maintenance releases.
GHSA-6jgm-4w45-vh8j at a Glance
Security Impact
CVSS: 9.9
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H).
How to Fix GHSA-6jgm-4w45-vh8j
To remediate this vulnerability, upgrade all affected Duplicate Advisory 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@Latest secure release
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 GHSA-6jgm-4w45-vh8j, inspect your project dependencies using npm:
npm ls vm2
Analyze the terminal output to locate any version of Duplicate Advisory in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than the patched release), 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-114: Process Control, where executing commands or loading libraries from an untrusted source or in an untrusted environment can cause an application to execute malicious commands (and payloads) on behalf of an attacker. In Duplicate Advisory, 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
GHSA-6jgm-4w45-vh8j Affected Duplicate Advisory Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
vm2
|
npm |
≥ 3.11.3
≤ 3.11.6
|
|
References
Frequently Asked Questions
What is GHSA-6jgm-4w45-vh8j?
Which Duplicate Advisory versions are affected?
What version fixes GHSA-6jgm-4w45-vh8j?
Is vm2 affected?
What is the CVSS score of GHSA-6jgm-4w45-vh8j?
What CWE is associated with GHSA-6jgm-4w45-vh8j?
How can I check npm dependencies for GHSA-6jgm-4w45-vh8j?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-6jgm-4w45-vh8j",
"modified" : "2026-10-01T15:28:21Z",
"published" : "2026-09-17T15:32:14Z",
"withdrawn" : "2026-10-01T15:28:21Z",
"aliases" : [ ],
"summary" : "Duplicate Advisory: vm2 crypto builtin loads attacker native code through setEngine",
"details" : "## Duplicate Advisory\n\nThis advisory has been withdrawn because it is a duplicate of GHSA-46pr-c5wc-xffx. This link is maintained to preserve external references.\n\n## Original Description\nvm2 3.11.3 through 3.11.6 exposes the host Node.js crypto module to a NodeVM sandbox when the crypto builtin is allowed. The module is presented via a recursive read-only proxy, but its callable exports still execute with host-process authority. Sandboxed JavaScript can therefore call crypto.setEngine() with a filesystem path to an attacker-supplied native library (for example, one bundled in an untrusted plugin package already written to disk); OpenSSL asks the operating-system dynamic loader to load the file, and the library's constructor executes native code in the host process before engine-symbol validation rejects it. Exploitation requires only the crypto builtin and does not require fs, process, module, child_process, worker_threads, vm, or inspector access, resulting in a sandbox escape and arbitrary native code execution. Fixed in 3.11.7.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H"
}, {
"type" : "CVSS_V4",
"score" : "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"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "vm2"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "3.11.3"
}, {
"last_affected" : "3.11.6"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/patriksimek/vm2/security/advisories/GHSA-46pr-c5wc-xffx"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-92939"
}, {
"type" : "WEB",
"url" : "https://www.vulncheck.com/advisories/vm2-3.11.3-through-3.11.6-native-code-execution-via-crypto-setengine"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-114" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2026-10-01T15:28:21Z",
"nvd_published_at" : "2026-09-17T14:17:58Z"
}
}