CVE-2026-92952

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.8 from GitHub Security Advisory (severity: MODERATE) published 2026-10-01. A secondary CVSS source baseline 6.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-81601 (ENISA EUVD) · GHSA-hmpr-c9rf-qcrf (GitHub Security Advisories) · GHSA-jf8q-945g-9q4c (GitHub Security Advisories)Source: ENISA EUVD

6.8EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 6.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.8MEDIUMmedium confidence
EG Risk
47
EG Risk 47/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity68% × 45%
Impact severity (EG Severity): CVSS 6.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
39th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.8): severity, escalated by confirmed exploitation. This CVE's 6.8 is its impact severity (EG Severity), not escalated.

EG Severity
6.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 17, 2026

Last Modified

September 17, 2026

Advisory Details (2)

Auto-updated Sep 17, 2026
Patch available. Sources: github.
Web page

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 advisoryMentions a patch (unverified)

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.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
npmvm2 @ 3.11.7 (fixes >= 3.11.4, <= 3.11.6)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
npm(1)
PackageVulnerable rangeFix by version rangeDependents
vm2—
  • 3.11.4 up to 3.11.7: fixed in 3.11.7
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 45× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 90 is merged into the row it repeats.

  1. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  2. 2026-11-01 07:37 UTCGHSA enrichmentGHSA-jf8q-945g-9q4c · GitHub severity MODERATE · GitHub CVSS 6.8
  3. 2026-11-01 07:37 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  5. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  8. 2026-10-28 02:55 UTCOSV refresh
  9. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  10. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  11. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  12. 2026-10-25 13:50 UTCEG score recompute
  13. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  14. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  16. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  17. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  18. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  19. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  20. 2026-10-18 02:59 UTCEG score recompute
  21. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  22. 2026-10-17 15:35 UTCEG score recompute
  23. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  24. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  25. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
Show 64 more
  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  2. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  3. 2026-10-12 14:44 UTCEG score recompute
  4. 2026-10-11 19:12 UTCEG score recompute
  5. 2026-10-11 16:29 UTCEG score recompute
  6. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  7. 2026-10-11 13:43 UTCEG score recompute
  8. 2026-10-11 03:43 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  10. 2026-10-09 22:57 UTCEG score recompute
  11. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  12. 2026-10-08 20:32 UTCEG score recompute
  13. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  15. 2026-10-06 15:43 UTCEG score recompute
  16. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  17. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  18. 2026-10-05 12:58 UTCEG score recompute
  19. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  20. 2026-10-04 10:34 UTCEG score recompute
  21. 2026-10-03 08:07 UTCEG score recompute
  22. 2026-10-02 05:40 UTCEG score recompute
  23. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  24. 2026-10-01 03:09 UTCEG score recompute
  25. 2026-10-01 03:09 UTCGHSA enrichmentGHSA-hmpr-c9rf-qcrf · GitHub severity HIGH · GitHub CVSS 6.8
  26. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  27. 2026-09-30 00:45 UTCEG score recompute
  28. 2026-09-30 00:45 UTCGHSA enrichmentGHSA-hmpr-c9rf-qcrf · GitHub severity HIGH · GitHub CVSS 6.8
  29. 2026-09-28 18:18 UTCEG score recompute
  30. 2026-09-28 18:18 UTCGHSA enrichmentGHSA-hmpr-c9rf-qcrf · GitHub severity HIGH · GitHub CVSS 6.8
  31. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  32. 2026-09-27 15:48 UTCEG score recompute
  33. 2026-09-27 15:48 UTCGHSA enrichmentGHSA-hmpr-c9rf-qcrf · GitHub severity HIGH · GitHub CVSS 6.8
  34. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  35. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  36. 2026-09-26 13:25 UTCEG score recompute
  37. 2026-09-26 13:24 UTCGHSA enrichmentGHSA-hmpr-c9rf-qcrf · GitHub severity HIGH · GitHub CVSS 6.8
  38. 2026-09-25 10:59 UTCEG score recompute
  39. 2026-09-25 10:58 UTCGHSA enrichmentGHSA-hmpr-c9rf-qcrf · GitHub severity HIGH · GitHub CVSS 6.8
  40. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  41. 2026-09-24 08:35 UTCEG score recompute
  42. 2026-09-24 08:35 UTCGHSA enrichmentGHSA-hmpr-c9rf-qcrf · GitHub severity HIGH · GitHub CVSS 6.8
  43. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  44. 2026-09-23 06:11 UTCEG score recompute
  45. 2026-09-23 06:11 UTCGHSA enrichmentGHSA-hmpr-c9rf-qcrf · GitHub severity HIGH · GitHub CVSS 6.8
  46. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  47. 2026-09-22 03:47 UTCEG score recompute
  48. 2026-09-22 03:47 UTCGHSA enrichmentGHSA-hmpr-c9rf-qcrf · GitHub severity HIGH · GitHub CVSS 6.8
  49. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  50. 2026-09-21 01:24 UTCEG score recompute
  51. 2026-09-21 01:24 UTCGHSA enrichmentGHSA-hmpr-c9rf-qcrf · GitHub severity HIGH · GitHub CVSS 6.8
  52. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  53. 2026-09-19 23:00 UTCEG score recompute
  54. 2026-09-19 23:00 UTCGHSA enrichmentGHSA-hmpr-c9rf-qcrf · GitHub severity HIGH · GitHub CVSS 6.8
  55. 2026-09-18 20:37 UTCEG score recompute
  56. 2026-09-18 20:37 UTCGHSA enrichmentGHSA-hmpr-c9rf-qcrf · GitHub severity HIGH · GitHub CVSS 6.8
  57. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.4% · 35th percentile
  58. 2026-09-17 17:58 UTCEG score recompute
  59. 2026-09-17 17:58 UTCGHSA enrichmentGHSA-hmpr-c9rf-qcrf · GitHub severity HIGH · GitHub CVSS 6.8
  60. 2026-09-17 15:49 UTCEG score recompute
  61. 2026-09-17 15:49 UTCGHSA enrichmentGHSA-hmpr-c9rf-qcrf · GitHub severity HIGH · GitHub CVSS 6.8
  62. 2026-09-17 14:22 UTCEG score recompute
  63. 2026-09-17 13:50 UTCEG score recomputeFirst assessed: 6.8 MEDIUM
  64. 2026-09-17 13:49 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-92952?
CVE-2026-92952 is a medium-severity vulnerability; its CVE record was 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 made public?
CVE-2026-92952 was made public on August 24, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 17, 2026. EchelonGraph's copy of the record carries a last-modified date of September 17, 2026; the record at its source may have been updated since.
Is CVE-2026-92952 actively exploited?
CVE-2026-92952 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (39th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92952?
CVE-2026-92952 has a CVSS base score of 6.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92952?
A fix for CVE-2026-92952 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-92952 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by 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.

Book a Demo →Browse All CVEs