CVE-2019-1458: Microsoft Win32k Privilege Escalation
Microsoft Win32k · listed in the CISA catalog of actively exploited vulnerabilities since 2022-01-10.
- CVSS v3.1 (CISA ADP)
- 7.8
- high
- EPSS (exploit probability, 30 days)
- 74%
- higher than 99.5% of all CVEs
- Added to CISA KEV
- 2022-01-10
- US federal due date 2022-07-10
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2019-1458 explained
CVE-2019-1458 is an elevation of privilege vulnerability in the Win32k component of Microsoft Windows. Win32k fails to properly handle objects in memory. CISA lists it as known to be exploited, including in ransomware campaigns, so unpatched Windows and Windows Server systems face a real risk of full takeover.
Impact
An attacker who can already run code on a system with low privileges can elevate those privileges. No user interaction is needed. Successful exploitation gives high impact to confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected system. The attack is local and not automatable at scale, but attackers are known to use it, including ransomware operators.
Who is affected
The CVE record lists Microsoft Windows editions, including 7 for 32-bit Systems Service Pack 1, 8.1 for x64-based systems, RT 8.1, 10 for x64-based Systems and 10 Version 1607 for 32-bit Systems, plus one more item. It also lists Microsoft Windows Server editions, including 2008 R2 for x64-based Systems Service Pack 1, 2008 for 32-bit Systems Service Pack 2, 2012, 2012 (Core installation) and 2012 R2, plus six more items. The CVE record names no fixed version.
Written with AI from the data on this page and checked against it automatically.
Official description
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in memory, aka 'Win32k Elevation of Privilege Vulnerability'.
CISA required action: Apply updates per vendor instructions.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft WindowsAffectedFixed in
- 7 for 32-bit Systems Service Pack 1
- 7 for x64-based Systems Service Pack 1
- 8.1 for 32-bit systems
- 8.1 for x64-based systems
- RT 8.1
- 10 for 32-bit Systems
- 10 for x64-based Systems
- 10 Version 1607 for 32-bit Systems
- 10 Version 1607 for x64-based Systems
not stated - Microsoft Windows ServerAffectedFixed in
- 2008 R2 for Itanium-Based Systems Service Pack 1
- 2008 R2 for x64-based Systems Service Pack 1
- 2008 for 32-bit Systems Service Pack 2
- 2008 for Itanium-Based Systems Service Pack 2
- 2008 for x64-based Systems Service Pack 2
- 2012
- 2012 (Core installation)
- 2012 R2
- 2012 R2 (Core installation)
- 2016
- 2016 (Core installation)
- 2008 for 32-bit Systems Service Pack 2 (Core installation)
- 2008 for x64-based Systems Service Pack 2 (Core installation)
- 2008 R2 for x64-based Systems Service Pack 1 (Core installation)
not stated
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows |
| not stated |
| Microsoft Windows Server |
| not stated |
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
- CISA's deadline for US federal agencies: 2022-07-10 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security updates for CVE-2019-1458 as described in the vendor advisory.
- Prioritize patching, since CISA lists this vulnerability as known exploited and used in ransomware.
- Inventory Windows and Windows Server systems to confirm every affected edition has received the update.
- Limit local and remote logon rights to reduce who can run code on affected systems.
- Check systems for signs of compromise, such as unexpected privileged accounts or processes.
The CVE record names no fixed version. Follow the Microsoft advisory for the correct update for each Windows edition, and follow CISA's required action: apply updates per vendor instructions. Until updates are installed, restrict who can log on to or run code on affected systems and monitor for signs of compromise.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Questions about CVE-2019-1458
- Is CVE-2019-1458 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-01-10 and notes known use in ransomware campaigns. The US federal due date was 2022-07-10.
- Can it be exploited remotely?
- The attack vector is local. An attacker needs to be able to run code on the system with low privileges first, then can use the flaw to gain full control.
- What should we do?
- Apply the Microsoft updates per the vendor advisory, as CISA requires. The CVE record does not list fixed version numbers, so use the advisory to identify the right update for each edition.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.