CVE-2026-92963

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-81613 (ENISA EUVD) · GHSA-xr25-qx3m-g53h (GitHub Security Advisories)Source: ENISA EUVD

5.3EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (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.3%CVSS: 5.3Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

vm2 versions before 3.11.2 fail to properly restrict access to the VM2_INTERNAL_STATE_DO_NOT_USE_OR_PROGRAM_WILL_FAIL global variable. Attackers can access this internal state object through globalThis to retrieve sensitive sandbox internals.

CVSS v3
5.3
EG Score
5.3MEDIUMmedium confidence
EG Risk
55
EG Risk 55/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)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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 at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
28th
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 (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-07). 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; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable yes (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)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (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 18, 2026

Advisory Details (2)

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

vm2 before 3.11.2 Information Disclosure via Internal State | Advisories | VulnCheck

https://www.vulncheck.com/advisories/vm2-before-3.11.2-information-disclosure-via-internal-state
GitHub advisoryMentions a patch (unverified)

Access to `VM2_INTERNAL_STATE_DO_NOT_USE_OR_PROGRAM_WILL_FAIL` · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-2cm2-m3w5-gp2f

Vendor Advisories for CVE-2026-92963(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.2: fixed in 3.11.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 33× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 114 rows on record for this CVE, as 99 entries (1 repeat merged).

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 100 is merged into the row it repeats. The 14 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:35 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  2. 2026-11-11 16:41 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  3. 2026-11-10 16:46 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  4. 2026-11-09 16:36 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  5. 2026-11-08 16:41 UTCEPSS rescoreEPSS 0.3% · 28th percentile
  6. 2026-11-07 19:08 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub severity MODERATE · GitHub CVSS 5.3
  7. 2026-11-07 19:08 UTCEchelonGraph re-scored
  8. 2026-11-07 16:40 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  9. 2026-11-06 16:40 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  10. 2026-11-05 16:39 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  11. 2026-11-04 16:37 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  12. 2026-11-03 16:49 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  13. 2026-11-02 16:46 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  14. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  15. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  16. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  17. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  18. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  19. 2026-10-28 02:55 UTCOSV refresh
  20. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  21. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  22. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.3% · 27th percentile
  23. 2026-10-25 13:50 UTCEchelonGraph re-scored
  24. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  25. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
Show 74 more
  1. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  2. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  3. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  4. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  5. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  6. 2026-10-18 02:59 UTCEchelonGraph re-scored
  7. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  8. 2026-10-17 15:35 UTCEchelonGraph re-scored
  9. 2026-10-17 15:35 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  10. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  11. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  12. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  13. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  14. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  15. 2026-10-12 14:44 UTCEchelonGraph re-scored
  16. 2026-10-11 20:58 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  17. 2026-10-11 19:12 UTCEchelonGraph re-scored
  18. 2026-10-11 16:29 UTCEchelonGraph re-scored
  19. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  20. 2026-10-11 13:43 UTCEchelonGraph re-scored
  21. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  22. 2026-10-10 19:59 UTCEchelonGraph re-scored
  23. 2026-10-10 19:59 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  24. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  25. 2026-10-09 19:00 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  26. 2026-10-08 18:03 UTCEchelonGraph re-scored
  27. 2026-10-08 18:03 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  28. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  29. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  30. 2026-10-07 14:30 UTCEchelonGraph re-scored
  31. 2026-10-07 14:30 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  32. 2026-10-06 15:19 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  33. 2026-10-06 13:20 UTCEchelonGraph re-scored
  34. 2026-10-06 13:20 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  35. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  36. 2026-10-05 12:23 UTCEchelonGraph re-scored
  37. 2026-10-05 12:23 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  38. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  39. 2026-10-04 11:24 UTCEchelonGraph re-scored
  40. 2026-10-04 11:24 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  41. 2026-10-03 10:27 UTCEchelonGraph re-scored
  42. 2026-10-03 10:27 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  43. 2026-10-02 09:29 UTCEchelonGraph re-scored
  44. 2026-10-02 09:29 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  45. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  46. 2026-10-01 08:31 UTCEchelonGraph re-scored
  47. 2026-10-01 08:31 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  48. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  49. 2026-09-30 07:32 UTCEchelonGraph re-scored
  50. 2026-09-30 07:32 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  51. 2026-09-29 06:34 UTCEchelonGraph re-scored
  52. 2026-09-29 06:34 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  53. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  54. 2026-09-28 05:35 UTCEchelonGraph re-scored
  55. 2026-09-28 05:35 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  56. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  57. 2026-09-27 04:37 UTCEchelonGraph re-scored
  58. 2026-09-27 04:37 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  59. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  60. 2026-09-26 03:34 UTCEchelonGraph re-scored
  61. 2026-09-26 03:34 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  62. 2026-09-25 02:24 UTCEchelonGraph re-scored
  63. 2026-09-25 02:24 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  64. 2026-09-24 14:04 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  65. 2026-09-24 01:25 UTCEchelonGraph re-scored
  66. 2026-09-24 01:25 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  67. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  68. 2026-09-23 00:28 UTCEchelonGraph re-scored
  69. 2026-09-23 00:28 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  70. 2026-09-22 16:01 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  71. 2026-09-21 23:29 UTCEchelonGraph re-scored
  72. 2026-09-21 23:28 UTCGHSA enrichmentGHSA-xr25-qx3m-g53h · GitHub CVSS 5.3
  73. 2026-09-21 21:09 UTCEPSS rescoreEPSS 0.2% · 10th percentile
  74. 2026-09-20 22:30 UTCEchelonGraph re-scored

Frequently asked(5)

What is CVE-2026-92963?
CVE-2026-92963 is a medium-severity vulnerability; its CVE record was published on September 17, 2026. vm2 versions before 3.11.2 fail to properly restrict access to the VM2_INTERNAL_STATE_DO_NOT_USE_OR_PROGRAM_WILL_FAIL global variable. Attackers can access this internal state object through globalThis to retrieve sensitive sandbox internals.
When was CVE-2026-92963 made public?
CVE-2026-92963 was made public on May 3, 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 18, 2026; the record at its source may have been updated since.
Is CVE-2026-92963 actively exploited?
CVE-2026-92963 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (28th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92963?
CVE-2026-92963 has a CVSS base score of 5.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92963?
A fix for CVE-2026-92963 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-92963 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-92963

Explore →

Is Your Infrastructure Affected by CVE-2026-92963?

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