dbcve.org
Graphics DriverApplication · Intel

CVE-2020-0502

MEDIUM · 5.3 CVSS v3.1 Published 2020-03-12
Fix available
A fix is available. Upgrade to 26.20.100.6912 or later.
See remediation →
55/100
Remediation priority · Elevated
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
Improper access control in Intel(R) Graphics Drivers before version 26.20.100.6912 may allow an authenticated user to potentially enable escalation of privilege via local access.

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 · moderate confidence

Improper access control in Intel(R) Graphics Drivers before version 26.20.100.6912 allows an authenticated local user to potentially escalate privileges. The vulnerability stems from insufficient access control checks within the graphics driver component, enabling a logged-in user to gain elevated system privileges.

MitigationUpdate Intel Graphics Drivers to version 26.20.100.6912 or later through Intel's driver update utilities or system vendor channels, then verify graphics functionality remains operational.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Graphics DriverApplication
Affected:< 26.20.100.6912

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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. Identify Intel Graphics Driver installation
    Open Device Manager, expand Display adapters, and confirm an Intel graphics device is listed (such as Intel UHD Graphics, Intel Iris Xe Graphics, or similar)
    Affected if An Intel graphics adapter appears under Display adapters in Device Manager
  2. Check installed Intel Graphics Driver version
    Right-click the Intel graphics device in Device Manager, select Properties, go to the Driver tab, and record the Driver Version number displayed
    Affected if The Driver Version field shows a version number for the Intel graphics driver
  3. Compare version against affected range
    Compare the installed Driver Version to 26.20.100.6912 using standard version number comparison - any version lower than 26.20.100.6912 falls within the affected range
    Affected if The installed version number is less than 26.20.100.6912

If the Intel Graphics Driver version is below 26.20.100.6912, the local privilege escalation vulnerability is present in the environment

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.

From vendor data
Upgrade available Upgrade to 26.20.100.6912 or later
Fixed in 26.20.100.6912
Interim mitigation

Update Intel Graphics Drivers to version 26.20.100.6912 or later through Intel's driver update utilities or system vendor channels, then verify graphics functionality remains operational.

Fix this in Graphics Driver Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-0502 — 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-2020-0502 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