---
id: GHSA-63m2-qqch-jxv2
title: >-
  Duplicate Advisory: vm2 leaks absolute host filesystem paths to sandbox code
  via error stack formatting
summary: >-
  Duplicate Advisory: vm2 leaks absolute host filesystem paths to sandbox code
  via error stack formatting
severity: medium
cvss: 5.8
cwe:
  - CWE-209
vendor: vm2
product: vm2
ecosystem: npm
affected:
  - 'vm2 >= 3.11.0, <= 3.11.6'
published: '2026-09-17'
updated: '2026-10-05'
sourceUpdated: '2026-10-05T22:35:19Z'
source: GHSA
sourceUrl: 'https://github.com/advisories/GHSA-63m2-qqch-jxv2'
references:
  - url: 'https://github.com/patriksimek/vm2/security/advisories/GHSA-x6m4-chr9-cg97'
  - url: 'https://nvd.nist.gov/vuln/detail/CVE-2026-92936'
  - url: >-
      https://www.vulncheck.com/advisories/vm2-3.11.0-before-3.11.7-information-disclosure-via-error-stack
  - url: 'https://github.com/advisories/GHSA-63m2-qqch-jxv2'
tags:
  - ghsa
  - npm
ingestedAt: '2026-10-05T22:35:24.741Z'
---

## Overview

## Duplicate Advisory

This advisory has been withdrawn because it is a duplicate of GHSA-x6m4-chr9-cg97. This link is maintained to preserve external references.

## Original Description
vm2 versions 3.11.0 through 3.11.6 leak absolute host filesystem paths to sandboxed code through error stack formatting. Attacker-supplied code can force the host-realm source transformer to throw a SyntaxError (for example by calling eval with malformed source) and then read the error's .stack property; the bridge forwards the .stack read to the host-realm formatter, bypassing the sandbox-side host-path redaction introduced for GHSA-v27g-jcqj-v8rw. The returned stack string discloses absolute paths from vm2, Node.js internals, and the embedding application's own source tree, along with host function names. Default new VM() and new NodeVM() configurations are affected without any special options, and the issue persists when string eval is disabled because the host-side transformer throws before eval is handled. The impact is information disclosure only; no code execution results. Fixed in vm2 3.11.7.

## Affected packages

- `vm2 >= 3.11.0, <= 3.11.6`

## Remediation

Refer to the advisory for the patched release.