CVE-2017-0001

CRITICALNVD 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-03-03), 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
9.0EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 3.1%CVSS: 7.8Exploit: cisa kev · ssvc activeExposed services: Not assessed

A fix is available — apply it.

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-0005, CVE-2017-0025, and CVE-2017-0047.

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation100% × 40%
Automatability0% × 15%
CISA SSVC: Track at low, Attend at medium and Act at high mission impact.
Action: A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
3.1%
EPSS %ILE
87th
KEV
⚠ Exploited

CISA SSVCTrack at low, Attend at medium and Act at high mission impact.

A fix is available. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

March 17, 2017

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated May 19, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: microsoft, cisa.
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-0001
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-0001
generic
http://www.securitytracker.com/id/1038002
generic
http://www.securityfocus.com/bid/96057

Vendor Advisories for CVE-2017-0001(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Data Freshness Timeline

(refreshed 92× in last 7d / 386× 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 1,597 total refreshes for this CVE.

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

Frequently asked(6)

What is CVE-2017-0001?
CVE-2017-0001 is a critical 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-0001 disclosed?
CVE-2017-0001 was first published on March 17, 2017, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2017-0001 actively exploited?
Yes. CISA added CVE-2017-0001 to the Known Exploited Vulnerabilities catalog on March 3, 2022, affecting Microsoft Graphics Device Interface (GDI). KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is available. Apply it.
What is the CVSS score of CVE-2017-0001?
CVE-2017-0001 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 (CRITICAL).
Which products are affected by CVE-2017-0001?
CVE-2017-0001 affects Microsoft Graphics Device Interface (GDI).
How do I remediate CVE-2017-0001?
A fix for CVE-2017-0001 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2017-0001 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2017-0001?

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

Book a Demo →Browse All CVEs