CriticalCVE-2018-8589

    Microsoft Win32k Privilege Escalation Vulnerability (CVE-2018-8589)

    Published In CISA KEV since Sources: CVE.org

    What is affected, what to do

    An elevation of privilege vulnerability exists when Windows improperly handles calls to Win32k.sys, aka "Windows Win32k Elevation of Privilege Vulnerability." This affects Windows Server 2008, Windows 7, Windows Server 2008 R2.

    The vulnerability is being actively exploited; treat it as a priority. The available sources name no fixed version. Check the vendor guidance in the references below. Immediate actions, mitigation and detection rules are in the runbook below.

    Affected
    • Microsoft Windows Server 2008 eq 32-bit Systems Service Pack 2..32-bit Systems Service Pack 2
    • Microsoft Windows Server 2008 eq 32-bit Systems Service Pack 2 (Server Core installation)..32-bit Systems Service Pack 2 (Server Core installation)
    • Microsoft Windows Server 2008 eq Itanium-Based Systems Service Pack 2..Itanium-Based Systems Service Pack 2
    • Microsoft Windows Server 2008 eq x64-based Systems Service Pack 2..x64-based Systems Service Pack 2
    • Microsoft Windows Server 2008 eq x64-based Systems Service Pack 2 (Server Core installation)..x64-based Systems Service Pack 2 (Server Core installation)
    • Microsoft Windows 7 eq 32-bit Systems Service Pack 1..32-bit Systems Service Pack 1
    • Microsoft Windows 7 eq x64-based Systems Service Pack 1..x64-based Systems Service Pack 1
    • Microsoft Windows Server 2008 R2 eq Itanium-Based Systems Service Pack 1..Itanium-Based Systems Service Pack 1
    • Microsoft Windows Server 2008 R2 eq x64-based Systems Service Pack 1..x64-based Systems Service Pack 1
    • Microsoft Windows Server 2008 R2 eq x64-based Systems Service Pack 1 (Server Core installation)..x64-based Systems Service Pack 1 (Server Core installation)

    Not sure whether and how you are affected? Ask a question about this vulnerability

    Metrics

    7.8

    Priority

    XIEM Effective CVSS: highest available CVSS rating from NVD and vendor data.

    Source: NVD, CVSS v3

    7.8

    CVSS v3

    Severity High on the scale from 0 to 10.

    Source: CVE.org

    3.0 %

    EPSS score

    Moderate — model estimates 1-10% exploitation likelihood.

    Source: FIRST EPSS, percentile 87.4

    Show all metrics
    Severity
    Critical
    Priority (0–325)

    The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?

    Read in glossary
    200.14 Methodology
    Exploit maturity

    An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.

    Read in glossary
    actively exploited
    XIEM Effective CVSS

    XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.

    Read in glossary
    7.8 Methodology
    CVSS v3

    CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.

    Read in glossary
    7.8
    EPSS score

    The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.

    Read in glossary
    3.0 %
    Moderate — model estimates 1-10% exploitation likelihood.
    EPSS percentile

    The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.

    Read in glossary
    87.4
    Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
    KEV status

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    Actively exploited
    Published
    In CISA KEV since

    The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.

    Read in glossary
    CISA assessment (SSVC)
    Exploitation: active · not automatable · Technical impact: total
    Source: CISA Vulnrichment, as of 7 February 2025

    Response and mitigation

    Why act now?

    Prioritisation rationale

    This bug was used as a zero-day in targeted attacks and acts as the second stage of a chain: after initial code execution via a document or browser exploit, the attacker escalates locally to SYSTEM without user interaction and gains full control over confidentiality, integrity and availability. CISA does not flag known ransomware use, and exploitation likelihood is moderate overall, though above the average CVE. If you have no Windows 7/2008 left in the estate, the risk is negligible; where such legacy systems persist — common in OT, lab and line-of-business environments at KRITIS operators — remediate with high priority, especially on multi-user hosts and machines where privileged accounts log on.

    1. Runbook step 1

      Immediate response (0-24 h)

      • Inventory affected hosts: Identify every Windows 7 SP1, Windows Server 2008 SP2 (incl. Server Core) and Windows Server 2008 R2 SP1 system from CMDB, AD (Get-ADComputer -Filter * -Properties OperatingSystem | ? OperatingSystem -match "2008|Windows 7") and EDR inventory. In Defender for Endpoint: DeviceTvmSoftwareVulnerabilities | where CveId == "CVE-2018-8589".
      • Deploy the security update: Microsoft has released a fix. Patch available from the vendor — look up the KB number per OS variant in the Microsoft Security Update Guide entry for CVE-2018-8589. Monthly Rollups are cumulative, so any later rollup that is correctly installed also closes the hole; verify via Get-HotFix or the win32k.sys file version.
      • Confirm end-of-life status: All affected operating systems are out of support. Treat any host without current patches as "unremediable", log it in the risk register (ISO 27001 A.8.8 / NIS2 Art. 21) and schedule migration.
      • Handle high-exposure legacy hosts first: Patch or isolate Windows Server 2008/2008 R2 terminal servers, Citrix/RDS hosts and jump servers first — many interactive users means the local foothold this exploit needs is easiest to obtain there.
      • Compromise assessment: On unpatched hosts, review the last 30 days of EDR telemetry for unexpected SYSTEM processes spawned from user context (see Detection rules). On a hit, isolate the host, capture memory, and rotate local and cached domain credentials.

    2. Runbook step 2

      Mitigation layers

      • Network segmentation: Move legacy Win7/2008 systems into a dedicated VLAN; allow only explicitly required inbound services and block direct outbound internet access (authenticated proxy only). Deny client-to-client SMB (445/tcp) and RDP (3389/tcp) to contain lateral movement after a successful escalation.
      • Application allowlisting: Enforce AppLocker (Windows 7 Enterprise/Ultimate, Server 2008 R2) and deny execution from %TEMP%, %APPDATA%, %LOCALAPPDATA%, Downloads and C:\Users\Public. Win32k exploits are typically dropped as an EXE/DLL into a user-writable path.
      • Cut off initial access: The bug requires local code execution, so close the entry vectors: block internet-sourced Office macros via GPO, remove outdated browsers/plugins from legacy hosts, and strip executable attachments at the mail gateway.
      • IAM / least privilege: Restrict interactive server logon ("Allow log on locally") to admin groups, keep privileged domain accounts off legacy systems (tiering model), and use LAPS for local administrator passwords.
      • Endpoint hardening: Ensure an EDR agent with kernel-exploit/token-manipulation detection runs on every legacy host (check vendor support for Win7/2008). Disable WDigest (UseLogonCredential=0) to limit cleartext credential theft once SYSTEM is obtained.

    3. Runbook step 3

      Detection rules

      • Privilege jump in the process tree (Sysmon EID 1 / Security 4688): Process running with IntegrityLevel=System or User=NT AUTHORITY\SYSTEM whose parent runs as a regular user and is not a service host. KQL: DeviceProcessEvents | where AccountSid == "S-1-5-18" and InitiatingProcessAccountSid != "S-1-5-18" and InitiatingProcessFileName !in~ ("services.exe","svchost.exe","wininit.exe","msiexec.exe").
      • SYSTEM shell from user context: cmd.exe, powershell.exe, rundll32.exe or whoami.exe holding a SYSTEM token, parented by an Office app, browser or unknown binary in %TEMP%/%APPDATA%. Sigma shape: selection: User|contains: 'SYSTEM' AND ParentImage|contains: ['\AppData\','\Temp\'].
      • Unknown binaries in writable paths: Sysmon EID 11 (FileCreate) followed by EID 1 for unsigned EXE/DLL in user directories executed shortly after creation; correlate with AppLocker events 8003/8004.
      • Post-escalation activity: Security 4697 / System 7045 (new service), Security 4720/4732 (account created / added to Administrators), Sysmon EID 10 with access to lsass.exe — alert at high severity on legacy hosts.
      • Crashes as a signal: Bugcheck events (System Event ID 1001, BugCheck) referencing win32k.sys on unpatched hosts may indicate failed exploitation attempts.

    Detection rules

    No NEOSEC detection rule is available for this vulnerability yet.

    Classification under NIS2 and CRA

    Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.

    NIS2

    NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.

    Read in glossary
    Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
    CRA

    The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.

    Read in glossary
    Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
    ISO/IEC 27001

    ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.

    Read in glossary
    Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.

    Description

    An elevation of privilege vulnerability exists when Windows improperly handles calls to Win32k.sys, aka "Windows Win32k Elevation of Privilege Vulnerability." This affects Windows Server 2008, Windows 7, Windows Server 2008 R2.

    Source: NVD (NIST), CISA KEV Catalog, cvelistv5

    Affected products

    The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.

    Affected products
    Affected versionsFixed in
    MicrosoftWindows 7
    • 32-bit Systems Service Pack 1
    • x64-based Systems Service Pack 1
    • —
    • —
    MicrosoftWindows Server 2008
    • x64-based Systems Service Pack 2 (Server Core installation)
    • 32-bit Systems Service Pack 2 (Server Core installation)
    • 32-bit Systems Service Pack 2
    • x64-based Systems Service Pack 2
    • Itanium-Based Systems Service Pack 2
    • —
    • —
    • —
    • —
    • —
    MicrosoftWindows Server 2008 R2
    • x64-based Systems Service Pack 1
    • Itanium-Based Systems Service Pack 1
    • x64-based Systems Service Pack 1 (Server Core installation)
    • —
    • —
    • —

    Vendors and products

    Affected operating systems

    Affected operating systems
    Windowsmicrosoftwindows_7—
    Windowsmicrosoftwindows_server_2008r2
    Windowsmicrosoftwindows_server_2008—

    Public exploit references

    Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.

    Public exploit references
    CISA KEV CatalogCISA Known Exploited Vulnerability (opens in a new tab)cisa.govactively exploited

    References & sources

    • securityfocus.com105796Vulnerability database, x_refsource_BID, Broken link, Third-party advisory, Vulnerability database
    • securitytracker.com1042140Vulnerability database, x_refsource_SECTRACK, Broken link, Third-party advisory, Vulnerability database
    • portal.msrc.microsoft.comen-US/security-guidance/advisory/CVE-2018-8589x_refsource_CONFIRM, Patch, Vendor advisory
    • cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2018-8589government-resource, US government resource
    Embed badge

    Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.

    Badge preview for CVE-2018-8589
    <a href="https://intel.neosec.eu/en/cve/CVE-2018-8589"><img src="https://intel.neosec.eu/badge/cve/CVE-2018-8589.svg?lang=en" alt="CVE-2018-8589 – NEOSEC Intel" height="20"></a>