CVE-2018-8639: Microsoft Windows Win32k Improper Resource Shutdown or Release
Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2025-03-03.
- CVSS v3.1 (CISA ADP)
- 8.4
- high
- EPSS (exploit probability, 30 days)
- 22%
- higher than 97.7% of all CVEs
- Added to CISA KEV
- 2025-03-03
- US federal due date 2025-03-24
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2018-8639 explained
CVE-2018-8639 is an elevation of privilege vulnerability in the Win32k component of Microsoft Windows, caused by improper handling of objects in memory (CWE-404). It affects a wide range of Windows client and server releases. CISA lists it as known to be exploited, including in ransomware campaigns, so unpatched systems are at real risk.
Impact
An attacker with local access can exploit the flaw to elevate privileges. CISA's assessment rates the technical impact as total, meaning full control of the affected system, with high impact to confidentiality, integrity and availability. The CVSS vector lists low attack complexity and no user interaction. CISA rates it as not automatable, so exploitation is not expected at scale without manual steps. Attackers are known to exploit it, and it is known to be used in ransomware campaigns.
Who is affected
The CVE record lists Windows 7 SP1, Windows 8.1, Windows RT 8.1, Windows 10 (several versions including 1607, 1703 and 1709, plus 7 more listed items), Windows Server 2008 SP2, Windows Server 2008 R2 SP1, Windows Server 2012, Windows Server 2012 R2, Windows Server 2016, Windows Server 2019 and Windows 10 Servers versions 1709 and 1803, including Server Core installations. The CVE record names no fixed version; check the Microsoft advisory for the applicable security updates.
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."
This affects Windows 7, Windows Server 2012 R2, Windows RT 8.1, Windows Server 2008, Windows Server 2019, Windows Server 2012, Windows 8.1, Windows Server 2016, Windows Server 2008 R2, Windows 10, Windows 10 Servers. This CVE ID is unique from CVE-2018-8641.
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
Affected and fixed versions
From the CVE record published by the vendor or CVE numbering authority.
- Microsoft Windows 7AffectedFixed in
- 32-bit Systems Service Pack 1
- x64-based Systems Service Pack 1
not stated - Microsoft Windows Server 2012 R2AffectedFixed in
- (Server Core installation)
not statedVersion statement as published by the CNA (free text).
- Microsoft Windows RT 8.1AffectedFixed in
- Windows RT 8.1
not stated - Microsoft Windows Server 2008AffectedFixed in
- Itanium-Based Systems Service Pack 2
- 32-bit Systems Service Pack 2
- x64-based Systems Service Pack 2
- 32-bit Systems Service Pack 2 (Server Core installation)
- x64-based Systems Service Pack 2 (Server Core installation)
not stated - Microsoft Windows Server 2019AffectedFixed in
- (Server Core installation)
not statedVersion statement as published by the CNA (free text).
- Microsoft Windows Server 2012AffectedFixed in
- (Server Core installation)
not statedVersion statement as published by the CNA (free text).
- Microsoft Windows 8.1AffectedFixed in
- 32-bit systems
- x64-based systems
not stated - Microsoft Windows Server 2016AffectedFixed in
- (Server Core installation)
not statedVersion statement as published by the CNA (free text).
- Microsoft Windows Server 2008 R2AffectedFixed in
- Itanium-Based Systems Service Pack 1
- x64-based Systems Service Pack 1
- x64-based Systems Service Pack 1 (Server Core installation)
not stated - Microsoft Windows 10AffectedFixed in
- 32-bit Systems
- x64-based Systems
- Version 1607 for 32-bit Systems
- Version 1607 for x64-based Systems
- Version 1703 for 32-bit Systems
- Version 1703 for x64-based Systems
- Version 1709 for 32-bit Systems
- Version 1709 for ARM64-based Systems
- Version 1709 for x64-based Systems
- Version 1803 for 32-bit Systems
- Version 1803 for ARM64-based Systems
- Version 1803 for x64-based Systems
- Version 1809 for 32-bit Systems
- Version 1809 for ARM64-based Systems
- Version 1809 for x64-based Systems
not stated - Microsoft Windows 10 ServersAffectedFixed in
- version 1709 (Server Core Installation)
- version 1803 (Server Core Installation)
not statedVersion statement as published by the CNA (free text).
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows 7 |
| not stated |
| Microsoft Windows Server 2012 R2Version statement as published by the CNA (free text). |
| not stated |
| Microsoft Windows RT 8.1 |
| not stated |
| Microsoft Windows Server 2008 |
| not stated |
| Microsoft Windows Server 2019Version statement as published by the CNA (free text). |
| not stated |
| Microsoft Windows Server 2012Version statement as published by the CNA (free text). |
| not stated |
| Microsoft Windows 8.1 |
| not stated |
| Microsoft Windows Server 2016Version statement as published by the CNA (free text). |
| not stated |
| Microsoft Windows Server 2008 R2 |
| not stated |
| Microsoft Windows 10 |
| not stated |
| Microsoft Windows 10 ServersVersion statement as published by the CNA (free text). |
| 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: 2025-03-24 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security update for CVE-2018-8639 to every affected Windows system, following the vendor advisory.
- Prioritize servers and systems where untrusted users can log on locally or run code.
- Replace or upgrade Windows releases that no longer receive security updates.
- Check systems for signs of compromise, such as unexpected privileged accounts or processes, given known ransomware use.
- Limit local and interactive logon rights to the users who need them.
The CVE record names no fixed version, but this does not mean no fix exists. Follow the Microsoft advisory to identify the security update for each Windows version. CISA requires applying mitigations per vendor instructions, following BOD 22-01 guidance for cloud services, or discontinuing use of the product if mitigations are unavailable. Restrict local access and monitor for compromise until patched.
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
Weakness: CWE-404 Improper Resource Shutdown or Release
Questions about CVE-2018-8639
- Is CVE-2018-8639 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2025-03-03 and notes known use in ransomware campaigns. US federal agencies had a due date of 2025-03-24.
- Can it be exploited remotely?
- The CVSS vector lists a local attack vector. An attacker needs to run code on the target system, then can gain elevated privileges and total control of it.
- Which fixed version should I install?
- The CVE record names no fixed version. Use the Microsoft vendor advisory to find the security update for each affected Windows release.
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-21. Always confirm with the vendor's or distribution's advisory before patching.