Skip to main content
Mallory
HighVulnerability

CVE-2017-8579: Microsoft Windows DirectX Elevation of Privilege Vulnerability

Published Jun 29, 2017 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.0High · v3
EPSS1.2%68th percentile
CISA KEVNoNot listed
In the wildReported2 exploitation records in Mallory
Vendor
Microsoft Corporation
IdentifiersCVE-2017-8579CWE-269

CVE-2017-8579 is an elevation-of-privilege vulnerability in the DirectX component of Microsoft Windows 10 Gold, versions 1511, 1607, and 1703, and Windows Server 2016. An authenticated attacker can use a specially crafted application to execute arbitrary code in kernel mode. Exploit activity has also been documented in a malicious-document delivery chain in which an embedded remote object in an RTF file exploited the vulnerability to retrieve follow-on content.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an authenticated attacker to execute arbitrary code in Windows kernel mode, resulting in elevation of privilege to kernel-level execution.

Mitigation

If you can’t patch tonight, do this now.

Until patches are fully deployed, reduce exposure by limiting the ability of untrusted or low-privileged users to execute arbitrary applications, enforcing application control policies, restricting interactive logon where not required, and monitoring for suspicious local processes attempting privilege escalation. Hardening measures that reduce initial code execution opportunities, such as attachment filtering and macro/script restrictions, may also reduce practical exploitation in multi-stage intrusion chains, but they do not eliminate the underlying vulnerability.

Remediation

Patch, then assume compromise.

Apply the Microsoft security update that addresses CVE-2017-8579 on all affected Windows 10 and Windows Server 2016 systems. Priority should be given to systems where untrusted users can execute code locally. Standard remediation also includes validating patch deployment across all affected builds and retiring unsupported or unpatched versions where possible.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10operating_system
Microsoft CorporationWindows Server 2016operating_system
FAQ

Frequently asked questions

Is CVE-2017-8579 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2017-8579?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2017-8579.
Is there a patch for CVE-2017-8579?
Apply the Microsoft security update that addresses CVE-2017-8579 on all affected Windows 10 and Windows Server 2016 systems. Priority should be given to systems where untrusted users can execute code locally.
What products are affected by CVE-2017-8579?
Microsoft Corporation Windows 10 and Microsoft Corporation Windows Server 2016.
How severe is CVE-2017-8579?
CVE-2017-8579 has a CVSS v3 score of 7.0 (High) and an EPSS score of 1.2% (68th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malware3Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.