CVE-2016-0167

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 2021-11-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 — 4 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 5.7%CVSS: 7.8Exploit: cisa kev · ssvc active · kev ransomwareExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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 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 referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
5.7%
EPSS %ILE
92nd
KEV
⚠ Exploited

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

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

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

April 12, 2016

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated May 19, 2026
⚠️ Active exploitation confirmed. Fix referenced — no release confirmed yet. Sources: cisa.
cisa🔴 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-2016-0167
generic

Microsoft Security Bulletin MS16-039 - Critical | Microsoft Learn

https://docs.microsoft.com/en-us/security-updates/securitybulletins/2016/ms16-039
generic
http://www.securitytracker.com/id/1035532
generic
http://www.securitytracker.com/id/1035529

Vendor Advisories for CVE-2016-0167(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 87× in last 7d / 385× 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,638 total refreshes for this CVE.

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

Frequently asked(6)

What is CVE-2016-0167?
CVE-2016-0167 is a critical vulnerability published on April 12, 2016. 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…
When was CVE-2016-0167 disclosed?
CVE-2016-0167 was first published on April 12, 2016, 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-2016-0167 actively exploited?
Yes. CISA added CVE-2016-0167 to the Known Exploited Vulnerabilities catalog on November 3, 2021, affecting Microsoft Win32k. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
What is the CVSS score of CVE-2016-0167?
CVE-2016-0167 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-2016-0167?
CVE-2016-0167 affects Microsoft Win32k.
How do I remediate CVE-2016-0167?
A fix for CVE-2016-0167 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2016-0167 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2016-0167

Explore →

Is Your Infrastructure Affected by CVE-2016-0167?

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

Book a Demo →Browse All CVEs