vm2: Sandbox Breakout Using Dangerous Host Proto Mutators

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-47698: 0.97% estimated exploitation activity in the next 30 days; percentile 61.95 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary VM2 suffers from a sandbox breakout vulnerability. This allows attackers to write code which can escape from the VM2 sandbox and execute arbitrary commands on the host system. Details The fix for https://github.com/patriksimek/vm2/security/advisories/GHSA-v6mx-mf47-r5wg is insufficient and can be bypassed by replacing indirectcall.call(dangerousmutator, ...) with indirectcall.call(indirectcall, dangerousmutator, ...) since indirect calls are not seen as dangerous. PoC Impact Attackers can perform Remote Code Execution under the assumption that the attacker can run arbitrary code execution inside the context of a vm2 sandbox.

Published by the source

17 Aug 2026, 17:32 UTC

Last modified by the source

30 Aug 2026, 15:06 UTC

Source last checked

26 Oct 2026, 13:01 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-cfcw-xp6x-25gj

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-cfcw-xp6x-25gj

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-cfcw-xp6x-25gj

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-47698

Advisory: vm2: Sandbox Breakout Using Dangerous Host Proto Mutators
IDs: CVE-2026-47698, GHSA-cfcw-xp6x-25gj
Record: https://patchnext.com/advisories/cve-2026-47698 (revision 3, source checked 26 Oct 2026, 13:01 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: vm2 3.11.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm vm2: affected <= 3.11.5; fixed in 3.11.6

## Suggested inspection (read-only)
- `npm ls vm2 --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on vm2.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-cfcw-xp6x-25gj (GitHub-reviewed advisory GHSA-cfcw-xp6x-25gj lists affected ranges: npm vm2 >=0 <=3.11.5)
- Verified: https://osv.dev/vulnerability/GHSA-cfcw-xp6x-25gj (OSV record GHSA-cfcw-xp6x-25gj lists affected ranges: npm vm2 >=0 <3.11.6 (fixed))

Commands are suggestions: review each one before running it.