CVE-2026-92960

CRITICALPre-NVD 10.010.0
EchelonGraph scoreMEDIUM confidence

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

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

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — Patch released this weekElevated

Also known asEUVD-2026-81610 (ENISA EUVD) · GHSA-qj2x-7x9q-qgm7 (GitHub Security Advisories)Source: ENISA EUVD

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

A fix is available — apply it.

vm2 before 3.11.6 fails to restrict access to os and dns builtins under the builtin: ['*'] configuration, allowing sandbox code to read host process identity and network topology. Attackers can invoke dns.setServers() to hijack the host process DNS resolver globally, redirecting all subsequent host DNS queries through an attacker-controlled resolver.

CVSS v3
10.0
EG Score
10.0CRITICALmedium confidence
EG Risk
76
EG Risk 76/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)
Severity100% × 45%
Impact severity (EG Severity): CVSS 10.0 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, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact total (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.5%
EPSS %ILE
41st
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 (10.0): severity, escalated by confirmed exploitation. This CVE's 10.0 is its impact severity (EG Severity), not escalated.

EG Severity
10.0 CRITICALCVSS-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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 3 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, Track* at medium and Attend at high mission impact.

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 total (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)3 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 total (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 Oct 30, 2026
🔬 Proof of concept available. Patch available. Sources: github.
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

NodeVM `builtin: ['*']` exposes `os` and `dns` — process-wide observability reads AND writes that hijack the host (sibling class of GHSA-9g8x-92q2-p28f) · Advisory · patriksimek/vm2 · GitHub

https://github.com/patriksimek/vm2/security/advisories/GHSA-m5w8-4gq2-6f8x
Web page

vm2 before 3.11.6 Process-wide State Exposure via os and dns | Advisories | VulnCheck

https://www.vulncheck.com/advisories/vm2-before-3.11.6-process-wide-state-exposure-via-os-and-dns

Patch Availability(6)

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—
  • every version up to 3.11.6: fixed in 3.11.6
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 27× in last 7d / 198× 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.

Showing the most recent 100 of 332 refreshes on record for this CVE.

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. None are among the latest 100 rows. The 232 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  2. 2026-11-01 12:42 UTCEG score recompute
  3. 2026-11-01 12:42 UTCVendor advisory
  4. 2026-11-01 12:42 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  5. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  6. 2026-10-31 14:46 UTCVendor advisory
  7. 2026-10-31 14:46 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  8. 2026-10-30 16:51 UTCEG score recompute
  9. 2026-10-30 16:51 UTCVendor advisory
  10. 2026-10-30 16:51 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  11. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-29 18:56 UTCEG score recompute
  13. 2026-10-29 18:56 UTCVendor advisory
  14. 2026-10-29 18:56 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  15. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-28 21:00 UTCEG score recompute
  17. 2026-10-28 21:00 UTCVendor advisory
  18. 2026-10-28 21:00 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  19. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-27 23:03 UTCEG score recompute
  21. 2026-10-27 23:03 UTCVendor advisory
  22. 2026-10-27 23:03 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  23. 2026-10-27 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  24. 2026-10-27 01:05 UTCEG score recompute
  25. 2026-10-27 01:05 UTCVendor advisory
Show 75 more
  1. 2026-10-27 01:05 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  2. 2026-10-26 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  3. 2026-10-25 23:23 UTCEG score recompute
  4. 2026-10-25 23:23 UTCVendor advisory
  5. 2026-10-25 23:22 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  6. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  7. 2026-10-25 13:50 UTCEG score recompute
  8. 2026-10-25 01:24 UTCEG score recompute
  9. 2026-10-25 01:24 UTCVendor advisory
  10. 2026-10-25 01:24 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  11. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  12. 2026-10-24 03:28 UTCEG score recompute
  13. 2026-10-24 03:28 UTCVendor advisory
  14. 2026-10-24 03:28 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  15. 2026-10-23 16:33 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  16. 2026-10-23 05:33 UTCEG score recompute
  17. 2026-10-23 05:33 UTCVendor advisory
  18. 2026-10-23 05:33 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  19. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.5% · 40th percentile
  20. 2026-10-22 07:35 UTCEG score recompute
  21. 2026-10-22 07:35 UTCVendor advisory
  22. 2026-10-22 07:35 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  23. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  24. 2026-10-21 09:37 UTCEG score recompute
  25. 2026-10-21 09:37 UTCVendor advisory
  26. 2026-10-21 09:37 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  27. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  28. 2026-10-20 11:42 UTCEG score recompute
  29. 2026-10-20 11:42 UTCVendor advisory
  30. 2026-10-20 11:41 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  31. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  32. 2026-10-19 13:39 UTCEG score recompute
  33. 2026-10-19 13:39 UTCVendor advisory
  34. 2026-10-19 13:39 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  35. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  36. 2026-10-18 13:29 UTCVendor advisory
  37. 2026-10-18 13:29 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  38. 2026-10-18 02:59 UTCEG score recompute
  39. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  40. 2026-10-17 15:34 UTCEG score recompute
  41. 2026-10-17 15:34 UTCVendor advisory
  42. 2026-10-17 15:34 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  43. 2026-10-17 05:24 UTCEG score recompute
  44. 2026-10-17 05:24 UTCVendor advisory
  45. 2026-10-17 05:24 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  46. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  47. 2026-10-16 06:59 UTCEG score recompute
  48. 2026-10-16 06:59 UTCVendor advisory
  49. 2026-10-16 06:58 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  50. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  51. 2026-10-15 05:42 UTCEG score recompute
  52. 2026-10-15 05:42 UTCVendor advisory
  53. 2026-10-15 05:42 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  54. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  55. 2026-10-14 01:20 UTCEG score recompute
  56. 2026-10-14 01:20 UTCVendor advisory
  57. 2026-10-14 01:20 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  58. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  59. 2026-10-12 21:33 UTCEG score recompute
  60. 2026-10-12 21:33 UTCVendor advisory
  61. 2026-10-12 21:33 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  62. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.5% · 39th percentile
  63. 2026-10-12 14:44 UTCEG score recompute
  64. 2026-10-12 01:58 UTCVendor advisory
  65. 2026-10-12 01:58 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  66. 2026-10-11 22:20 UTCVendor advisory
  67. 2026-10-11 22:20 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  68. 2026-10-11 19:12 UTCEG score recompute
  69. 2026-10-11 18:39 UTCVendor advisory
  70. 2026-10-11 18:39 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  71. 2026-10-11 16:29 UTCEG score recompute
  72. 2026-10-11 14:48 UTCEG score recompute
  73. 2026-10-11 14:48 UTCVendor advisory
  74. 2026-10-11 14:48 UTCGHSA enrichmentGHSA-qj2x-7x9q-qgm7 · GitHub severity CRITICAL · GitHub CVSS 10.0
  75. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.5% · 39th percentile

Frequently asked(5)

What is CVE-2026-92960?
CVE-2026-92960 is a critical-severity vulnerability; its CVE record was published on September 17, 2026. vm2 before 3.11.6 fails to restrict access to os and dns builtins under the builtin: ['*'] configuration, allowing sandbox code to read host process identity and network topology. Attackers can invoke dns.setServers() to hijack the host process DNS resolver globally, redirecting all subsequent host…
When was CVE-2026-92960 made public?
CVE-2026-92960 was made public on August 14, 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-92960 actively exploited?
CVE-2026-92960 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (41st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-92960?
CVE-2026-92960 has a CVSS base score of 10.0 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-92960?
A fix for CVE-2026-92960 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-92960 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-92960

Explore →

Is Your Infrastructure Affected by CVE-2026-92960?

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