CVE-2026-92952

MEDIUMPre-NVD 6.86.8—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this weekElevated
6.8EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 6.8Exploit: Elevated riskExposed: 0

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

vm2 versions 3.11.4 through 3.11.6 incompletely filter Node.js registered internal symbols across the sandbox boundary. The extraction filters in lib/setup-sandbox.js and the cross-realm symbol checks and write traps in lib/bridge.js use a fixed list of known dangerous registered symbols that omits nodejs.stream.disturbed and nodejs.stream.errored, which are exposed on host WebStream prototypes on newer Node.js releases (validated on Node.js v25.8.0). When the embedder exposes a host WebStream object and the host stream/web module to the sandbox, sandbox code can obtain the real host symbols via Object.getOwnPropertySymbols(streamWeb.ReadableStream.prototype) and use them as write keys on host stream objects, corrupting host-visible stream state — for example making stream.Readable.isDisturbed() return false for an already-consumed stream. This can bypass host logic that relies on Node's public stream-state helpers to enforce one-shot body consumption, reject errored streams, or decide whether a stream is safe to hand to another component. It is not a host code-execution primitive in the reported proof of vulnerability. This is an incomplete fix for the earlier nodejs.* symbol filtering issue. Fixed in vm2 3.11.7.

CVSS v3
6.8
EG Score
6.8(high)
EG Risk
47(Track)
EG Risk 47/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
Severity68% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
36%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 17, 2026

Advisory Details (2)

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

vm2 3.11.4 through 3.11.6 Sandbox Symbol Filtering Bypass | Advisories | VulnCheck

https://www.vulncheck.com/advisories/vm2-3.11.4-through-3.11.6-sandbox-symbol-filtering-bypass
github Patch Available🟡 PoC Available

Incomplete nodejs.* symbol filtering lets sandbox override host WebStream state checks · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-jf8q-945g-9q4c

Vendor Advisories for CVE-2026-92952(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 10× in last 7d / 10× 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-18 20:37 UTCEG score recompute
  2. 2026-09-18 20:37 UTCGHSA enrichment
  3. 2026-09-18 19:28 UTCEPSS rescore
  4. 2026-09-17 17:58 UTCEG score recompute
  5. 2026-09-17 17:58 UTCGHSA enrichment
  6. 2026-09-17 15:49 UTCEG score recompute
  7. 2026-09-17 15:49 UTCGHSA enrichment
  8. 2026-09-17 14:22 UTCEG score recompute
  9. 2026-09-17 13:50 UTCEG score recompute
  10. 2026-09-17 13:49 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-92952?
CVE-2026-92952 is a medium vulnerability published on September 17, 2026. vm2 versions 3.11.4 through 3.11.6 incompletely filter Node.js registered internal symbols across the sandbox boundary. The extraction filters in lib/setup-sandbox.js and the cross-realm symbol checks and write traps in lib/bridge.js use a fixed list of known dangerous registered symbols that omits…
When was CVE-2026-92952 disclosed?
CVE-2026-92952 was first published in the National Vulnerability Database on September 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-92952 actively exploited?
CVE-2026-92952 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 64.1% of all scored CVEs.
What is the CVSS score of CVE-2026-92952?
CVE-2026-92952 has a CVSS v3 base score of 6.8 (NVD).
How do I remediate CVE-2026-92952?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-92952, 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-92952

Explore →

Is Your Infrastructure Affected by CVE-2026-92952?

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

Start Free Scan →Browse All CVEs