Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.2amended

vm2: Host-returned Promise rejection can bypass vm2's unhandled-rejection hardening and terminate the host process

CVE-2026-92954GHSA-gjq8-xm47-88rc

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (vm2 3.11.8), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm vm2

    Affected
    >= 3.10.0, <= 3.11.7
    Fixed in
    3.11.8

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
9.2 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:H · score source
EPSS
  • CVE-2026-92954: 0.49% estimated exploitation activity in the next 30 days; percentile 42.06 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary vm2 current head (v3.11.5, commit 7a1f5100b96f48d34e0fe104ab37c0acc5944f92) can still be used to terminate the host Node.js process when sandbox code calls a host-realm function that returns a rejected host Promise and then ignores the returned value. This is an incomplete-fix variant of the GHSA-hw58-p9xv-2mjh unhandled rejection hardening. The localPromise constructor now catches and consumes sandbox-created unhandled rejections, but host Promises returned across the bridge are not marked handled at the bridge boundary. If the sandbox does not attach .catch() or .then(..., onRejected), Node's default unhandled rejection behavior terminates the host process. Technical Details lib/setup-sandbox.js hardens sandbox-created Promises by wrapping the executor and attaching a benign swallow tail: That only applies to localPromise instances created inside the sandbox. Host-returned Promises cross the membrane through the bridge apply path. The bridge wraps callbacks when sandbox…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-gjq8-xm47-88rc

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GHSA-gjq8-xm47-88rc

  4. Revision 1 · created ·

    Published from ghsa record GHSA-gjq8-xm47-88rc

Agent brief

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

# Patch Next advisory brief: CVE-2026-92954

Advisory: vm2: Host-returned Promise rejection can bypass vm2's unhandled-rejection hardening and terminate the host process
IDs: CVE-2026-92954, GHSA-gjq8-xm47-88rc
Record: https://patchnext.com/advisories/cve-2026-92954 (revision 4, source checked 26 Oct 2026, 13:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.2)
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.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm vm2: affected >= 3.10.0, <= 3.11.7; fixed in 3.11.8

## 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-gjq8-xm47-88rc (GitHub-reviewed advisory GHSA-gjq8-xm47-88rc lists affected ranges: npm vm2 >=3.10.0 <=3.11.7)
- Verified: https://osv.dev/vulnerability/GHSA-gjq8-xm47-88rc (OSV record GHSA-gjq8-xm47-88rc lists affected ranges: npm vm2 >=3.10.0 <3.11.8 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…