How severe is CVE-2017-0001?

CVE-2017-0001 has a CVSS score of 7.8/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-0001?

Affected package information for CVE-2017-0001 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2017-0001?

No fixed release is recorded for CVE-2017-0001 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.

How do I detect CVE-2017-0001 in my code and dependencies?

Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).

How do I mitigate CVE-2017-0001 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Is CVE-2017-0001 actively exploited in the wild?

Yes. There are 2 known exploit references for CVE-2017-0001, including 2 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-0001?

CVE-2017-0001 has an EPSS (Exploit Prediction Scoring System) score of 3.1%, placing it in the 88th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

Is CVE-2017-0001 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2017-0001 (Microsoft Graphics Device Interface (GDI) Privilege Escalation Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-03-03. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-03-24. The required action was: Apply updates per vendor instructions. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

When was CVE-2017-0001 published, and has it been updated?

CVE-2017-0001 was published on March 17, 2017 and was last updated on October 21, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🛡️

CISA KEV · ACTIVELY EXPLOITED

HIGH severity

CVE-2017-0001 — Microsoft

HIGH

CVE-2017-0001 is a high-severity (CVSS 7.8) vulnerability. It is in CISA's Known Exploited Vulnerabilities catalog (added 2022-03-03) — treat it as actively exploited and patch now. No vendor fix is recorded yet; mitigation options are listed below.

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;…

Published

Mar 17, 2017

Updated

Oct 21, 2025

Affected

10 products

Patched

See advisory

Exploits

2 known

Exploitation data as of Oct 28, 2026 · OSV.dev, NVD, CISA KEV, FIRST.org (EPSS)

Exploitation Status

Actively exploited in the wild

Confirmed by CISA's Known Exploited Vulnerabilities catalog on 2022-03-03. Federal agencies were required to remediate by 2022-03-24.
A successful exploit gives an attacker total control of the affected component, not partial access.

Exploitation and automatability from CISA (KEV catalog and SSVC triage) for CVE-2017-0001.

EPSS Exploitation Probability

via FIRST.org ↗

3.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2017-0001 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 396,966 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Description

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.

Affected Products

10 products · 15 configurations

windows 7microsoft

all

windows 8.1microsoft

all

windows 10 1507microsoft

all

windows 10 1511microsoft

all

windows 10 1607microsoft

all

windows rt 8.1microsoft

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

The Graphics Device Interface (GDI) in Microsoft Windows Vista SP2; Wind…

mandiant.comAPIMay 2017

The Graphics Device Interface (GDI) in Microsoft Windows Vista SP2; Wind…

cisa.govCISAMar 2022

Detection & mitigation playbook

Vulnerability

Detect
Identify every host running the affected component and compare the installed build against the fixed version below — for source-built or distro-packaged software the version string, not a lockfile, is the source of truth (`dpkg -l`, `rpm -q`, or the binary's own `--version`).
Remediation status
No fixed release is recorded for CVE-2017-0001 yet. Track the upstream advisory, and apply the exposure-reduction steps below in the meantime.
Mitigate without a patch
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-0001 in your dependencies?

Find it across , including transitive dependencies.

Scan my dependencies How O3 SCA works