Actively exploited

CVE-2018-8611 Microsoft Windows Kernel Privilege Escalation Vulnerability

A privilege escalation vulnerability exists when the Windows kernel fails to properly handle objects in memory.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch urgentlyCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 24 May 2022.
  • Rated High severity (CVSS 7.8, scored by CISA).
  • It has been in the catalogue for 1,627 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

An elevation of privilege vulnerability exists when the Windows kernel fails to properly handle objects in memory, aka "Windows Kernel 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.

Affected Versions

ProductVersions
Microsoft Windows 732-bit Systems Service Pack 1
x64-based Systems Service Pack 1
Microsoft Windows Server 2012 R2(Server Core installation)
Microsoft Windows RT 8.1Windows RT 8.1
Microsoft Windows Server 200832-bit Systems Service Pack 2
32-bit Systems Service Pack 2 (Server Core installation)
Itanium-Based Systems Service Pack 2
x64-based Systems Service Pack 2
x64-based Systems Service Pack 2 (Server Core installation)
Microsoft Windows Server 2019(Server Core installation)
Microsoft Windows Server 2012(Server Core installation)

From the public CVE record, as supplied by the vendor. Always confirm against the vendor advisory.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Microsoft Windows. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply updates per vendor instructions.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2018-8611 and every other exploited flaw on the list.

Check My Exposure