---
id: GHSA-6jgm-4w45-vh8j
title: >-
  Duplicate Advisory: vm2 crypto builtin loads attacker native code through
  setEngine
summary: >-
  Duplicate Advisory: vm2 crypto builtin loads attacker native code through
  setEngine
severity: critical
cvss: 9.9
cwe:
  - CWE-114
vendor: vm2
product: vm2
ecosystem: npm
affected:
  - 'vm2 >= 3.11.3, <= 3.11.6'
published: '2026-09-17'
updated: '2026-10-01'
sourceUpdated: '2026-10-01T15:28:22Z'
source: GHSA
sourceUrl: 'https://github.com/advisories/GHSA-6jgm-4w45-vh8j'
references:
  - url: 'https://github.com/patriksimek/vm2/security/advisories/GHSA-46pr-c5wc-xffx'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-92939'
  - url: >-
      https://www.vulncheck.com/advisories/vm2-3.11.3-through-3.11.6-native-code-execution-via-crypto-setengine
  - url: 'https://github.com/advisories/GHSA-6jgm-4w45-vh8j'
tags:
  - ghsa
  - npm
ingestedAt: '2026-10-01T15:48:17.827Z'
---

## Overview

## Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-46pr-c5wc-xffx. This link is maintained to preserve external references.

## Original Description
vm2 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.

## Affected packages

- `vm2 >= 3.11.3, <= 3.11.6`

## Remediation

Refer to the advisory for the patched release.
