dbcve.org
Out-of-bounds ReadWeakness · CWE-125

CVE-2026-20751

HIGH · 8.3 CVSS v4.0 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
85/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Out-of-bounds read 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 exposure. 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 (high), integrity (none) and availability (high) of the vulnerable system, resulting in subsequent system confidentiality (high), integrity (none) and availability (high) impacts.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

An out-of-bounds read vulnerability exists in Intel Data Center Graphics Driver for VMware ESXi software before version 2.0.2. The flaw is in the device driver running at Ring 1 (privileged kernel mode), allowing a privileged local attacker to potentially expose sensitive data through memory access beyond allocated buffers, leading to denial of service.

MitigationUpdate the Intel Data Center Graphics Driver for VMware ESXi to version 2.0.2 or later to address the vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:H/SC:H/SI:N/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify the host is VMware ESXi
    Run 'vmware -v' or check /etc/vmware/version to confirm the hypervisor
    Affected if The system is not VMware ESXi (this driver is specific to ESXi)
  2. Confirm Intel Data Center Graphics Driver is present
    Check for the driver module via 'vmkload_mod -l' or look for igfx driver files in /usr/lib/vmware/vmkmod/
    Affected if The Intel Data Center Graphics Driver is not installed
  3. Identify the installed driver version
    Run 'vmkload_mod -s igfx' or check the driver metadata file for version information
    Affected if Version is lower than 2.0.2 (vulnerable versions are before 2.0.2)
  4. Verify the driver is loaded in memory
    Run 'vmkload_mod -l | grep igfx' to confirm the module is active
    Affected if Driver is not loaded (the vulnerability only applies when the driver is running)

A user is affected if they are running VMware ESXi with Intel Data Center Graphics Driver version lower than 2.0.2 and the driver is loaded

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Intel Data Center Graphics Driver for VMware ESXi to version 2.0.2 or later to address the vulnerability.

Recommended fix Moderate confidence

Intel(R) Data Center Graphics Driver for VMware ESXi version 2.0.2

  1. 1. Identify the current version of Intel(R) Data Center Graphics Driver installed on the VMware ESXi system by running: esxcli software vib list | grep -i intel or checking VMware ESXi host profile
  2. 2. Download the Intel Data Center Graphics Driver version 2.0.2 or later from the VMware website or Intel's official support page
  3. 3. Upload the driver VIB to a datastore accessible by the ESXi host
  4. 4. Install the new driver on the ESXi host using: esxcli software vib install -d /vmfs/volumes/<datastore>/<driver-bundle.zip>
  5. 5. Reboot the ESXi host to apply the driver changes: esxcli system shutdown reboot -r "Updating Intel graphics driver to 2.0.2"
  6. 6. After reboot, verify the new driver version is installed: esxcli software vib list | grep -i intel
  7. 7. If running a cluster, repeat steps 3-6 for all affected ESXi hosts
Caveat Ensure driver compatibility with your specific VMware ESXi version before upgrading; test in a staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-20751 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-20751 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data