CVE-2026-92948

CRITICALPre-NVD 9.99.9
EchelonGraph scoreHIGH confidence

Score 9.9 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-17. a secondary CVSS source baseline 9.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
9.9EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.9Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

vm2 versions >= 3.9.6 and <= 3.11.6 are affected by a NodeVM builtin allowlist bypass that permits a sandbox escape on Node.js 24 and newer when the embedder explicitly allows the node:test builtin (e.g. require: { builtin: ['node:test'] }). On Node.js 24+, module.builtinModules exposes the scheme-only key node:test, which is not covered by vm2's family-based DANGEROUS_BUILTINS protection, so it is stored in the generic host-passthrough loader. Because requireImpl() in lib/setup-node-sandbox.js strips a single 'node:' prefix before the builtin lookup, sandbox code calling require('node:node:test') resolves to the stored node:test key and receives a readonly proxy to the host module. Calls to node:test.run() are forwarded to the host implementation, which spawns a separate Node process for process-isolated test execution and passes through attacker-controlled execArgv values; supplying --eval= therefore executes arbitrary JavaScript in an unrestricted host Node process outside the NodeVM sandbox. Fixed in vm2 3.11.7.

CVSS v3
9.9
EG Score
9.9(high)
EG Risk
61(Track*)
EG Risk 61/100SSVC: Track*

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity99% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Watch closely — could escalate to Attend.
EPSS PROB
0%
EPSS %ILE
38%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 18, 2026

Advisory Details (2)

Auto-updated Sep 18, 2026
🔬 Proof of concept available. Patch available. Sources: github.
generic

vm2 3.9.6 through 3.11.5 Sandbox Escape via node:test | Advisories | VulnCheck

https://www.vulncheck.com/advisories/vm2-3.9.6-through-3.11.5-sandbox-escape-via-node-test
github Patch Available🟡 PoC Available

NodeVM builtin allowlist bypass via node:test.run() execArgv allows sandbox escape · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-qhwx-74w5-xhxq

Vendor Advisories for CVE-2026-92948(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 22× in last 7d / 22× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-19 22:38 UTCGHSA enrichment
  2. 2026-09-19 18:18 UTCEG score recompute
  3. 2026-09-19 18:18 UTCGHSA enrichment
  4. 2026-09-19 13:58 UTCGHSA enrichment
  5. 2026-09-19 09:36 UTCGHSA enrichment
  6. 2026-09-19 05:14 UTCGHSA enrichment
  7. 2026-09-19 00:54 UTCGHSA enrichment
  8. 2026-09-18 20:35 UTCEG score recompute
  9. 2026-09-18 20:35 UTCGHSA enrichment
  10. 2026-09-18 19:44 UTCEG score recompute
  11. 2026-09-18 19:44 UTCGHSA enrichment
  12. 2026-09-18 19:28 UTCEPSS rescore
  13. 2026-09-18 17:05 UTCGHSA enrichment
  14. 2026-09-18 12:45 UTCGHSA enrichment
  15. 2026-09-18 08:25 UTCGHSA enrichment
  16. 2026-09-18 04:05 UTCGHSA enrichment
  17. 2026-09-17 23:43 UTCGHSA enrichment
  18. 2026-09-17 18:55 UTCEG score recompute
  19. 2026-09-17 18:54 UTCGHSA enrichment
  20. 2026-09-17 14:22 UTCEG score recompute
  21. 2026-09-17 13:50 UTCEG score recompute
  22. 2026-09-17 13:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92948?
CVE-2026-92948 is a critical vulnerability published on September 17, 2026. vm2 versions >= 3.9.6 and <= 3.11.6 are affected by a NodeVM builtin allowlist bypass that permits a sandbox escape on Node.js 24 and newer when the embedder explicitly allows the node:test builtin (e.g. require: { builtin: ['node:test'] }). On Node.js 24+, module.builtinModules exposes the…
When was CVE-2026-92948 disclosed?
CVE-2026-92948 was first published in the National Vulnerability Database on September 17, 2026, with the most recent update on September 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92948 actively exploited?
CVE-2026-92948 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 61.7% of all scored CVEs.
What is the CVSS score of CVE-2026-92948?
CVE-2026-92948 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2026-92948?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92948, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-92948

Explore →

Is Your Infrastructure Affected by CVE-2026-92948?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.