Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-92954 high CVSS 8.6

Vulnerability in vm2 (CVE-2026-92954)

Summary

Vulnerability in vm2 (CVE-2026-92954). Risk of unauthorized operations or information disclosure. Exploitable via localPromise. Mitigation: upgrade to 3.11.8 or later.

Original description

The description as published by the source.

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:

apply(globalPromisePrototypeThen, this, [undefined, localPromiseSwallow]);

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 code later calls .then, .catch, or .finally on a host Promise:

bridge.setHostPromiseSanitizers(e => handleException(from(e)), from);

However, if sandbox code ignores the returned host Promise, no host-side rejection handler is attached. The original host Promise remains unhandled and Node terminates the host process under the default unhandled-rejection behavior.

`NodeV…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-92954 has been found in vm2.
Attackers can target a specific entry point like localPromise over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 8.6/10.
What to do: upgrade vm2 to 3.11.8 or later.
If unsure, ask your IT team or search "vm2 CVE-2026-92954" on the vendor's site.

CVE-2026-92954 (vm2) — CWE-248 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: localPromise / NodeVM / events / EventEmitter.once
Patched: 3.11.8 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-248) exists in vm2. Attackers reach the vulnerable code path via localPromise without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of vm2. Attack surface: localPromise / NodeVM / events / EventEmitter.once.

🔥 Severity

Severity: High (CVSS 8.6/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 3.11.8.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'vm2' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'vm2' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で vm2 を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade vm2 to 3.11.8

    ステージング環境で 3.11.8 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm vm2
[{"type":"SEMVER","events":[{"introduced":"3.10.0"},{"fixed":"3.11.8"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details