CVE-2026-92962

LOWPre-NVD 2.12.1
EchelonGraph scoreMEDIUM confidence

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

This low-severity CVE scores 2.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (4th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-81612 (ENISA EUVD) · GHSA-2c9f-f88g-g76p (GitHub Security Advisories)Source: ENISA EUVD

2.1EG
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.2%CVSS: 2.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

vm2 is a sandbox for running untrusted JavaScript. In vm2 versions up to and including 3.11.3, the defaultSandboxPrepareStackTrace function in lib/setup-sandbox.js builds its output array using prototype-walking index assignment (lines[lines.length] = value) rather than a prototype-bypassing define-property primitive. Because this bridge-internal array is allocated in the sandbox realm, code inside the sandbox can install an accessor on Array.prototype for the relevant index; the accessor is then invoked whenever the sandbox reads error.stack (or otherwise triggers Error.prepareStackTrace), allowing sandbox code to observe and intercept each stack-trace line written by the bridge. The same pattern is used in the error-handling (catch) branch. The values written are formatted strings only, so the practical impact is limited to an information side channel and a violation of vm2's bridge-container defense invariant rather than a sandbox escape; the vendor rates the issue Low. The issue is fixed in vm2 3.11.4, which installs each entry as an own data property via Reflect.defineProperty.

CVSS v3
2.1
EG Score
2.1LOWmedium confidence
EG Risk
25
EG Risk 25/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)
Severity21% × 45%
Impact severity (EG Severity): CVSS 2.1 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.2%
EPSS %ILE
4th
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 (2.1): severity, escalated by confirmed exploitation. This CVE's 2.1 is its impact severity (EG Severity), not escalated.

EG Severity
2.1 LOWCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-29). 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

References (2)

Vendor Advisories for CVE-2026-92962(1)

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

Affected Packages

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 43× 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 71 is merged into the row it repeats.

  1. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  4. 2026-10-29 17:47 UTCEG score recompute
  5. 2026-10-29 17:47 UTCGHSA enrichmentGHSA-2c9f-f88g-g76p · GitHub severity LOW
  6. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-27 06:55 UTCOSV refresh
  10. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-25 13:50 UTCEG score recompute
  13. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  18. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-18 02:59 UTCEG score recompute
  20. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  22. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.2% · 4th percentile
Show 45 more
  1. 2026-10-12 14:44 UTCEG score recompute
  2. 2026-10-11 19:12 UTCEG score recompute
  3. 2026-10-11 16:29 UTCEG score recompute
  4. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-10-11 13:43 UTCEG score recompute
  6. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-09 23:28 UTCEG score recompute
  8. 2026-10-09 23:28 UTCGHSA enrichmentGHSA-2c9f-f88g-g76p · GitHub severity LOW
  9. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-07 04:47 UTCEG score recompute
  13. 2026-10-07 04:47 UTCGHSA enrichmentGHSA-2c9f-f88g-g76p · GitHub severity LOW
  14. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  17. 2026-10-04 10:06 UTCEG score recompute
  18. 2026-10-04 10:06 UTCGHSA enrichmentGHSA-2c9f-f88g-g76p · GitHub severity LOW
  19. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  20. 2026-10-01 15:25 UTCEG score recompute
  21. 2026-10-01 15:25 UTCGHSA enrichmentGHSA-2c9f-f88g-g76p · GitHub severity LOW
  22. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  23. 2026-09-28 20:44 UTCEG score recompute
  24. 2026-09-28 20:44 UTCGHSA enrichmentGHSA-2c9f-f88g-g76p · GitHub severity LOW
  25. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  26. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  27. 2026-09-26 02:03 UTCEG score recompute
  28. 2026-09-26 02:03 UTCGHSA enrichmentGHSA-2c9f-f88g-g76p · GitHub severity LOW
  29. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.2% · 3rd percentile
  30. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  31. 2026-09-23 07:19 UTCEG score recompute
  32. 2026-09-23 07:19 UTCGHSA enrichmentGHSA-2c9f-f88g-g76p · GitHub severity LOW
  33. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  34. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  35. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  36. 2026-09-20 12:38 UTCEG score recompute
  37. 2026-09-20 12:38 UTCGHSA enrichmentGHSA-2c9f-f88g-g76p · GitHub severity LOW
  38. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.2% · 6th percentile
  39. 2026-09-17 17:58 UTCEG score recompute
  40. 2026-09-17 17:58 UTCGHSA enrichmentGHSA-2c9f-f88g-g76p · GitHub severity LOW
  41. 2026-09-17 15:44 UTCEG score recompute
  42. 2026-09-17 15:44 UTCGHSA enrichmentGHSA-2c9f-f88g-g76p · GitHub severity LOW
  43. 2026-09-17 14:22 UTCEG score recompute
  44. 2026-09-17 13:50 UTCEG score recomputeFirst assessed: 2.1 LOW
  45. 2026-09-17 13:49 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-92962?
CVE-2026-92962 is a low-severity vulnerability; its CVE record was published on September 17, 2026. vm2 is a sandbox for running untrusted JavaScript. In vm2 versions up to and including 3.11.3, the defaultSandboxPrepareStackTrace function in lib/setup-sandbox.js builds its output array using prototype-walking index assignment (lines[lines.length] = value) rather than a prototype-bypassing…
When was CVE-2026-92962 made public?
CVE-2026-92962 was made public on May 18, 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-92962 actively exploited?
CVE-2026-92962 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92962?
CVE-2026-92962 has a CVSS base score of 2.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92962?
A fix for CVE-2026-92962 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-92962 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-92962

Explore →

Is Your Infrastructure Affected by CVE-2026-92962?

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

Book a Demo →Browse All CVEs