Vulnerability record · CVE-2016-0167 · published 12 April 2016
CVE-2016-0167: Microsoft Windows Win32k kernel driver privilege escalation
Microsoft · Windows 10 1507
The kernel-mode Win32k driver in multiple Windows versions fails to properly handle objects, letting a local user run a crafted application to gain elevated privileges. It is a distinct Win32k elevation-of-privilege flaw from CVE-2016-0143 and CVE-2016-0165, and Microsoft addressed it in MS16-039. Because it is a kernel privilege escalation listed in CISA KEV with known ransomware use, it matters for post-compromise escalation on unpatched hosts.
Description
The kernel-mode driver 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 and 1511 allows local users to gain privileges via a crafted application, aka "Win32k Elevation of Privilege Vulnerability," a different vulnerability than CVE-2016-0143 and CVE-2016-0165.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Automated analysis
high priorityIt is a kernel privilege escalation with confirmed exploitation and known ransomware use per CISA KEV, though it requires local access and user interaction and has a moderate EPSS probability.
What it is
The kernel-mode Win32k driver in multiple Windows versions fails to properly handle objects, letting a local user run a crafted application to gain elevated privileges. It is a distinct Win32k elevation-of-privilege flaw from CVE-2016-0143 and CVE-2016-0165, and Microsoft addressed it in MS16-039. Because it is a kernel privilege escalation listed in CISA KEV with known ransomware use, it matters for post-compromise escalation on unpatched hosts.
Impact
An attacker who can run code locally gains full privileges on the host, typically SYSTEM, enabling credential theft, persistence and defense evasion. CISA records known ransomware campaign use, so it can be chained into broader intrusions.
Attack surface
Reached locally by executing a crafted application on an affected Windows system; the CVSS vector is AV:L with UI:R, so the attacker needs local access and some form of user interaction, and no prior privileges (PR:N). No remote or network vector is described.
Exploitation
CISA KEV lists it as exploited, added 2021-11-03 with known ransomware campaign use, and EPSS 30-day probability is about 5.7 percent (92.7th percentile). The reference set contains only patch, vendor advisory and government catalog links, with no public exploit or PoC tags.
What to do
- Apply the MS16-039 security update from Microsoft to all affected Windows versions; this is the primary fix.
- Retire or isolate unsupported platforms such as Windows Vista SP2 and Windows Server 2008 SP2/R2 SP1 that no longer receive updates.
- Restrict local interactive logon and application execution to trusted users, since the flaw requires local code execution.
- Enable exploit protection features such as ASLR, DEP and Control Flow Guard, and block untrusted executables via application control.
- Monitor for and remove commodity malware and ransomware tooling that uses Win32k privilege escalation.
Detection
- Hunt for unexpected processes gaining SYSTEM or high-integrity tokens shortly after user-launched applications, especially on unpatched Windows 7, 8.1, RT 8.1, Server 2008/2012 and Windows 10 1507/1511 hosts.
- Alert on execution of known exploit or ransomware binaries that target Win32k privilege escalation, correlating with CISA KEV guidance.
- Audit patch state for MS16-039 across the affected product list and flag hosts missing the update.
- Review local process creation and token-manipulation telemetry for crafted applications spawning elevated children from medium-integrity parents.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Exploitation in the wild
CISA added CVE-2016-0167 to the Known Exploited Vulnerabilities catalog on 3 November 2021 as "Microsoft Win32k Privilege Escalation Vulnerability". CISA reports known use in ransomware campaigns. Required action: Apply updates per vendor instructions. Federal deadline 3 May 2022.
Affected products
8 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| http://www.securitytracker.com/id/1035529 | Broken LinkThird Party AdvisoryVDB Entry |
| http://www.securitytracker.com/id/1035532 | Broken LinkThird Party AdvisoryVDB Entry |
| https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-039 | PatchVendor Advisory |
| http://www.securitytracker.com/id/1035529 | Broken LinkThird Party AdvisoryVDB Entry |
| http://www.securitytracker.com/id/1035532 | Broken LinkThird Party AdvisoryVDB Entry |
| https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-039 | PatchVendor Advisory |
| https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2016-0167 | US Government Resource |
Track CVE-2016-0167 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2016-0167), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.