---
id: CVE-2026-92939
title: >-
  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
summary: >-
  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 au…
severity: critical
cvss: 9.9
cvssVector: 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H'
cwe:
  - CWE-114
vendor: patriksimek
product: vm2
affected:
  - vm2 >= 3.11.3 < 3.11.7
published: '2026-09-17'
updated: '2026-09-17'
sourceUpdated: '2026-09-17T15:17:00.650'
source: NVD
sourceUrl: 'https://nvd.nist.gov/vuln/detail/CVE-2026-92939'
references:
  - url: 'https://github.com/patriksimek/vm2/security/advisories/GHSA-46pr-c5wc-xffx'
    label: disclosure@vulncheck.com
  - url: >-
      https://www.vulncheck.com/advisories/vm2-3.11.3-through-3.11.6-native-code-execution-via-crypto-setengine
    label: disclosure@vulncheck.com
  - url: 'https://github.com/patriksimek/vm2/security/advisories/GHSA-46pr-c5wc-xffx'
    label: 134c704f-9b21-4f2e-91b3-4a467353bcc0
tags:
  - nvd
  - cve.org
  - exploit-available
exploitAvailable: true
ssvc:
  exploitation: poc
  automatable: 'no'
  technicalImpact: total
  timestamp: '2026-09-17T14:26:12.253959Z'
ingestedAt: '2026-09-17T14:19:30.984Z'
epss: 0.00616
epssPercentile: 0.47307
---

## Overview

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.

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.