vm2 Has a Sandbox Breakout Using Async Generator

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-45411: 0.57% estimated exploitation activity in the next 30 days; percentile 47.13 (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 It is possible to catch a host exception using the yield expression inside an async generator. When the generator is closed using the return function, the value is awaited on and exceptions thrown in the then call will be catched by the runtime and passed to the yield iterator as the next value. PoC Impact Attackers can perform Remote Code Execution under the assumption that arbitrary code can be executed inside the context of a vm2 sandbox.

Published by the source

14 May 2026, 21:14 UTC

Last modified by the source

14 May 2026, 21:41 UTC

Source last checked

26 Oct 2026, 12:52 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-248r-7h7q-cr24

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-248r-7h7q-cr24

3. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-248r-7h7q-cr24

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

# Patch Next advisory brief: CVE-2026-45411

Advisory: vm2 Has a Sandbox Breakout Using Async Generator
IDs: CVE-2026-45411, GHSA-248r-7h7q-cr24
Record: https://patchnext.com/advisories/cve-2026-45411 (revision 3, source checked 26 Oct 2026, 12:52 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.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm vm2: affected <= 3.11.2; fixed in 3.11.3

## 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-248r-7h7q-cr24 (GitHub-reviewed advisory GHSA-248r-7h7q-cr24 lists affected ranges: npm vm2 >=0 <=3.11.2)
- Verified: https://osv.dev/vulnerability/GHSA-248r-7h7q-cr24 (OSV record GHSA-248r-7h7q-cr24 lists affected ranges: npm vm2 >=0 <3.11.3 (fixed))

Commands are suggestions: review each one before running it.