Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-92940 critical CVSS 10.0

Vulnerability in vm2 (CVE-2026-92940)

Summary

Vulnerability in vm2 (CVE-2026-92940). Confidential information can be exposed externally. Exploitable via Host header. Mitigation: upgrade to 3.11.7 or later.

Original description

The description as published by the source.

Summary

vm2 3.11.6 exposes the host process's real https.globalAgent when a NodeVM is explicitly allowed to require https. The module is wrapped as read-only, but calls to methods on the shared agent still mutate the host object. Sandbox code can register a free listener and receive host request options and the host TLS socket whenever an unrelated host HTTPS request releases a pooled connection.

In a contained test, sandbox code allowed only the https builtin:

  • read the host request's bearer token from the agent event;
  • attached a data listener to the released host TLS socket and read the next host response body in plaintext;
  • learned the private service host and port;
  • sent an attacker-chosen authenticated POST using the stolen host token; and
  • received confirmation that the service accepted the action.

The host application never passed its credentials, request, response, socket, or destination into the sandbox. They crossed the boundary solely because vm2 exposes the process-global HTTPS agent instead of a sandbox-local network module instance.

Details

The vulnerable boundary is the default builtin loader in lib/builtin.js:

builtins.set(key, special ? special : vm => vm.readonly(hostRequire(key)));

The wrapper recursively exposes properties of the actual host module. For ordinary constants, a read-only proxy can be sufficient. It is not sufficient for process-global EventEmitter objects whose methods mutate internal state.

`https.glo…

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-92940 has been found in vm2.
Attackers can target a specific entry point like Host header over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 10.0/10.
What to do: upgrade vm2 to 3.11.7 or later.
If unsure, ask your IT team or search "vm2 CVE-2026-92940" on the vendor's site.

CVE-2026-92940 (vm2) — CWE-668 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Host header / https.globalAgent / NodeVM / https
Patched: 3.11.7 — 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-668) exists in vm2. Attackers reach the vulnerable code path via Host header without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of vm2. Attack surface: Host header / https.globalAgent / NodeVM / https.

🔥 Severity

Severity: Critical (CVSS 10.0/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 3.11.7.

🛡️ 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.7

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

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

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

Affected packages

npm vm2
[{"type":"SEMVER","events":[{"introduced":"3.11.3"},{"fixed":"3.11.7"}]}]

References

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