CVE-2017-0005

HIGHNVD 7.89.0
EchelonGraph scoreHIGH confidence

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-05-24), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, ghsa, nvd
Trending — 5 sources updated this weekExploited in the wild
7.8
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS: 11%CVSS: 7.8Exploit: NoneExposed: 0

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

The Graphics Device Interface (GDI) in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; and Windows 10 Gold, 1511, and 1607 allows local users to gain privileges via a crafted application, aka "Windows GDI Elevation of Privilege Vulnerability." This vulnerability is different from those described in CVE-2017-0001, CVE-2017-0025, and CVE-2017-0047.

CVSS v3
7.8
EG Score
9.0(high)
EPSS
95.4%
KEV
⚠ Exploited

Published

March 17, 2017

Last Modified

April 22, 2026

Advisory Details (4)

Auto-updated May 19, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: cisa, microsoft.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2017-0005
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-0005

Weakness Classification(1)

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

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 91× in last 7d / 377× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 639 total refreshes for this CVE.

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

Frequently asked(6)

What is CVE-2017-0005?
CVE-2017-0005 is a high vulnerability published on March 17, 2017. The Graphics Device Interface (GDI) in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; and Windows 10 Gold, 1511, and 1607 allows local users to gain privileges via a crafted application, aka "Windows GDI…
When was CVE-2017-0005 disclosed?
CVE-2017-0005 was first published in the National Vulnerability Database on March 17, 2017, with the most recent update on April 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-0005 actively exploited?
Yes. CISA added CVE-2017-0005 to the Known Exploited Vulnerabilities catalog on May 24, 2022, affecting Microsoft Windows. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2017-0005?
CVE-2017-0005 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0.
Which products are affected by CVE-2017-0005?
CVE-2017-0005 affects Microsoft Windows. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2017-0005?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2017-0005, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2017-0005

Explore →

Is Your Infrastructure Affected by CVE-2017-0005?

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