CVE-2026-20879

HIGHNVD 8.38.3
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.3 under NVD CVSS v3. EPSS exploit probability: 0.1% (1st percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-29531 (ENISA EUVD) · GHSA-m6jr-w5q8-7x85 (GitHub Security Advisories)Source: ENISA EUVD

8.3EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 8.3Exploit: None knownExposed services: Not assessed

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

The CVE record's description, written by its CNA (Intel Corporation), states the affected versions: "Out-of-bounds write for the Intel(R) Data Center Graphics Driver for VMware ESXi software before version 2.0.2 within Ring 1: Device Drivers may allow a denial of service." No release containing a fix is confirmed on record.

Out-of-bounds write for the Intel(R) Data Center Graphics Driver for VMware ESXi software before version 2.0.2 within Ring 1: Device Drivers may allow a denial of service. System software adversary with a privileged user combined with a low complexity attack may enable data corruption. This result may potentially occur via local access when attack requirements are not present without special internal knowledge and requires no user interaction. The potential vulnerability may impact the confidentiality (none), integrity (high) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (none), integrity (high) and availability (high) impacts.

CVSS v3
8.3
EG Score
8.3HIGHmedium confidence
EG Risk
37
EG Risk 37/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)
Severity83% × 45%
Impact severity (EG Severity): CVSS 8.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (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: No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.
EPSS PROB
0.1%
EPSS %ILE
1st
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 (8.3): severity, escalated by confirmed exploitation. This CVE's 8.3 is its impact severity (EG Severity), not escalated.

EG Severity
8.3 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-24). 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 every mission impact level.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: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

No fix is confirmed yet. Restrict network exposure of the affected system within your standard update timelines, and watch for a fix.

Exploitation none (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.

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

May 12, 2026

Last Modified

May 13, 2026

Advisory Details (1)

Auto-updated May 12, 2026
No fix on record yet.
Web page

INTEL-SA-01402

https://intel.com/content/www/us/en/security-center/advisory/intel-sa-01402.html

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 35× 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 99 of 262 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. 1 repeat row among the latest 100 is merged into the row it repeats. The 163 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-20879?
CVE-2026-20879 is a high-severity vulnerability; its CVE record was published on May 12, 2026. Out-of-bounds write for the Intel(R) Data Center Graphics Driver for VMware ESXi software before version 2.0.2 within Ring 1: Device Drivers may allow a denial of service. System software adversary with a privileged user combined with a low complexity attack may enable data corruption. This result…
When was the CVE record for CVE-2026-20879 published?
The CVE record for CVE-2026-20879 was published on May 12, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of May 13, 2026; the record at its source may have been updated since.
Is CVE-2026-20879 actively exploited?
CVE-2026-20879 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (1st percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-20879?
CVE-2026-20879 has a CVSS v3 base score of 8.3 (NVD).
How do I remediate CVE-2026-20879?
No fix for CVE-2026-20879 is confirmed yet. Until one is published, restrict network exposure of the affected system — for example, keep it off the internet or limit it to trusted networks — and watch for a fix. The CVE record's description, written by its CNA (Intel Corporation), states the affected versions: "Out-of-bounds write for the Intel(R) Data Center Graphics Driver for VMware ESXi software before version 2.0.2 within Ring 1: Device Drivers may allow a denial of service." No release containing a fix is confirmed on record.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-20879

Explore →

Is Your Infrastructure Affected by CVE-2026-20879?

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

Book a Demo →Browse All CVEs