Synced 17 Jun 2026 22:27 UTC Account
← Intel Graphics Driver

Intel Graphics Driver vulnerabilities: known CVEs & security history

Intel · Driver / Firmware · 62 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Intel Graphics Driver release lines — 62 in total. A CVE here doesn't mean your version is affected — check Intel Graphics Driver's current status and the safe version to run.

62
known CVEs
0
actively exploited (KEV)
0
critical severity
0
ransomware-linked

Known Intel Graphics Driver CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2018-12220 high 8.2 0% 2019
CVE-2018-12216 high 8.2 0% 2019
CVE-2018-12214 high 8.2 0% 2019
CVE-2020-0565 high 7.8 0% 2020
CVE-2020-0520 high 7.8 0% 2020
CVE-2020-0519 high 7.8 0% 2020
CVE-2020-0515 high 7.8 0% 2020
CVE-2020-0514 high 7.8 0% 2020
CVE-2020-0508 high 7.8 0% 2020
CVE-2020-0504 high 7.8 0% 2020
CVE-2019-11111 high 7.8 0% 2019
CVE-2019-11112 high 7.8 0% 2019
CVE-2019-0155 high 7.8 1% 2019
CVE-2018-12221 high 7.8 0% 2019
CVE-2018-12152 high 7.8 1% 2018
CVE-2017-5727 high 7.8 0% 2018
CVE-2017-5696 high 7.8 1% 2018
CVE-2017-5717 high 7.8 1% 2017
CVE-2016-5647 high 7.8 1% 2016
CVE-2025-32453 medium 6.7 0% 2026
CVE-2025-32092 medium 6.7 0% 2026
CVE-2018-18091 medium 6.5 0% 2019
CVE-2018-12212 medium 6.5 0% 2019
CVE-2018-12211 medium 6.5 0% 2019
CVE-2018-12210 medium 6.5 0% 2019
CVE-2018-12153 medium 6.5 0% 2018
CVE-2018-3611 medium 6.5 2% 2018
CVE-2018-12223 medium 6.3 0% 2019
CVE-2022-42879 medium 6.1 0% 2023
CVE-2020-0505 medium 6.1 0% 2020
CVE-2018-12215 medium 6 0% 2019
CVE-2018-12213 medium 6 0% 2019
CVE-2021-0120 medium 5.5 0% 2021
CVE-2021-0012 medium 5.5 0% 2021
CVE-2020-0567 medium 5.5 0% 2020
CVE-2020-0516 medium 5.5 1% 2020
CVE-2020-0511 medium 5.5 0% 2020
CVE-2020-0503 medium 5.5 0% 2020
CVE-2020-0501 medium 5.5 0% 2020
CVE-2019-14591 medium 5.5 0% 2019
CVE-2019-14590 medium 5.5 0% 2019
CVE-2019-14574 medium 5.5 0% 2019
CVE-2019-11089 medium 5.5 0% 2019
CVE-2019-0115 medium 5.5 0% 2019
CVE-2019-0113 medium 5.5 0% 2019
CVE-2018-18090 medium 5.5 0% 2019
CVE-2018-18089 medium 5.5 0% 2019
CVE-2018-12219 medium 5.5 0% 2019
CVE-2017-5692 medium 5.5 0% 2018
CVE-2020-0517 medium 5.3 0% 2020
CVE-2020-0502 medium 5.3 0% 2020
CVE-2019-0114 medium 4.7 0% 2019
CVE-2020-0507 medium 4.4 0% 2020
CVE-2019-11113 medium 4.4 0% 2019
CVE-2019-0116 medium 4.4 0% 2019
CVE-2018-12224 low 3.3 0% 2019
CVE-2018-12222 low 3.3 0% 2019
CVE-2018-12218 low 3.3 0% 2019
CVE-2018-12209 low 3.3 0% 2019
CVE-2025-32739 low 2.8 0% 2026
CVE-2020-0506 low 2.3 0% 2020
CVE-2018-12217 low 2.3 0% 2019

Is my Intel Graphics Driver version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Intel Graphics Driver version → · Monitor Intel Graphics Driver for new CVEs →

Intel Graphics Driver vulnerabilities — frequently asked

How many known vulnerabilities does Intel Graphics Driver have?

IsItPatched tracks 62 CVEs for Intel Graphics Driver. 0 are critical-severity and 19 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Intel Graphics Driver have any actively-exploited vulnerabilities?

None of Intel Graphics Driver's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Intel Graphics Driver vulnerability?

Among tracked issues, CVE-2018-12220 (HIGH, CVSS 8.2) ranks highest.

Is Intel Graphics Driver safe to use?

It depends on the version. The latest supported Intel Graphics Driver release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Intel Graphics Driver security status · Intel Graphics Driver end-of-life · actively-exploited CVEs. Always verify against Intel's advisories — see our disclaimer.