Skip to content
English

Patch first › Microsoft

Exploited RansomwareCVE from 2018, added in 2025

CVE-2018-8639

Microsoft Windows · Operating systems

Microsoft Windows Win32k Improper Resource Shutdown or Release Vulnerability

At a glance

Exploited. Added to CISA’s catalog of exploited vulnerabilities on March 3, 2025.

Used in ransomware attacks, according to CISA.

Affected product: Microsoft Windows (category Operating systems, indicative classification). Name in CISA’s catalog: Microsoft Windows.

What should I do?

Apply the patches or mitigations from Microsoft; if none are available, stop using the product. For cloud services, follow the guidance from Microsoft.

Deadline set by CISA for US federal agencies: 21 days (due March 24, 2025). It only binds those agencies, but it is a useful measure of urgency.

Original text of the required action (CISA)

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

Timeline

  1. Vulnerability published Publication date (NVD)
  2. Exploitation confirmed Added to CISA’s KEV catalog
  3. CISA deadline Remediation deadline set for US federal agencies

The facts, with their sources

Exploitation confirmed
Yes, on March 3, 2025 Date added to the catalog of exploited vulnerabilities. Exploitation itself may have started earlier. Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
Ransomware
Known use Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
Hunt for compromise
Not requested by CISA Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
CISA required action
Apply the patches or mitigations from Microsoft; if none are available, stop using the product. For cloud services, follow the guidance from Microsoft. Rewritten by this site from CISA’s original text. Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
CISA deadline
March 24, 2025, 21 days Set for US federal agencies: a measure of urgency, not an obligation elsewhere. Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
Microsoft patch
Not available Source: Security Update Guide, collected September 29, 2026 at 14:57 UTC
Vulnerability published
December 12, 2018 Source: National Vulnerability Database (NVD), collected September 29, 2026 at 15:00 UTC
Product according to CISA
Microsoft Windows Filed by this site under “Operating systems” (indicative classification). Source: KEV catalog, collected September 29, 2026 at 14:57 UTC
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Technical detail of the score: attack vector, complexity, impact. Source: National Vulnerability Database (NVD), collected September 29, 2026 at 15:00 UTC

Severity and activity

7.8 / 10 CVSS severity: high

Score from the NVD. Collected Sep 29, 2026.

— Probability of exploitation in the next 30 days (EPSS)

FIRST’s EPSS model. Since exploitation is already confirmed, this figure is mostly useful to compare activity. Collected Sep 29, 2026.

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.

Official description from the NVD, collected Sep 29, 2026. CVE® description © The MITRE Corporation.

Microsoft Windows Win32k contains an improper resource shutdown or release vulnerability that allows for local, authenticated privilege escalation. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode.

Summary from CISA (KEV catalog).

CERT-FR advisories

No advisory among the latest CERT-FR publications this site follows. That does not mean there are none.

Information reused under the Open Licence 2.0 (Etalab); the date of last update is shown for each advisory. This site is neither affiliated with nor endorsed by ANSSI.

Sources for this page