Exploited CVEs / Microsoft / CVE-2016-0165
CVE-2016-0165
Microsoft Win32k Privilege Escalation Vulnerability. Exploitation in the wild is confirmed by CISA, not predicted. Federal agencies were required to remediate by 2023-07-13 (that deadline has passed); treat that date as the outer bound for your own environment. The fix is in the vendor advisory: Microsoft Security Update Guide (MSRC), linked below.
Risk summary
Actively exploited Microsoft Win32k vulnerability. Added to the CISA KEV catalog 2023-06-22.
Senserva AI Opinion for CVE-2016-0165
A decade old this year, this Win32k privilege escalation still earns its KEV listing (2023-06-22) because kernel escalation bugs remain useful long after disclosure: any code running as a user can leverage it toward SYSTEM. Severity is High. The machines at risk are the unpatched Windows holdouts, which are precisely the machines attackers can still find.
Do this: Sweep for Windows hosts missing 2016-era kernel updates and patch or retire them.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2016-0165
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2016-0165
- Published
- 2023-06-22
- Last revised
- 2023-06-22
- Changes tracked
- 1
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
CISA required action
Federal remediation due date: 2023-07-13 (past due).
Official fix for CVE-2016-0165
The authoritative fix and affected-version list are published by the vendor. Find the Win32k advisory on Microsoft Security Update Guide (MSRC).
Common questions about CVE-2016-0165
Is CVE-2016-0165 actively exploited?
Yes. CVE-2016-0165 was added to the CISA Known Exploited Vulnerabilities (KEV) catalog on 2023-06-22, which means exploitation in the wild has been confirmed, not predicted.
What is the CISA deadline and required action for CVE-2016-0165?
CISA set the federal remediation due date at 2023-07-13, which has passed; treat any unremediated system as overdue.
What fixes CVE-2016-0165?
The authoritative fix is in the vendor advisory: see Microsoft Security Update Guide (MSRC) for the patched Win32k versions and any workarounds. KEV listing makes this a fix-first item: patch it ahead of higher-CVSS issues nobody is exploiting.
Can I ask my own AI about CVE-2016-0165?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2016-0165's key facts: severity, CVSS, EPSS, the KEV date, the CISA due date, and the required action. Copy it into Claude, ChatGPT, or Copilot; the data is refreshed twice a day (morning and afternoon US Central).
Scope and sources
- More exploited Microsoft CVEs
- CVE-2019-1068CVE-2008-4250CVE-2009-1537CVE-2010-0249CVE-2010-0806CVE-2026-41091CVE-2026-45498CVE-2026-33825
All Microsoft exploited CVEs on one page: Microsoft vulnerabilities actively exploited.
- Authoritative references
Every actively exploited CVE, searchable with due dates and CSV export: the exploited-CVE tracker. The newest additions: exploited this week.