# CVE-2018-8611: Microsoft Windows Kernel Privilege Escalation

> An attacker can exploit improper memory object handling in the Windows kernel to elevate privileges on affected systems.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 24 May 2022 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Dec 2018
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-24mr-rp5r-phj8

## What is CVE-2018-8611?

CVE-2018-8611 is a high-severity vulnerability in Microsoft Windows 10 1607, published on 12 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2018-8611?

It affects 12 products.


Products: Microsoft Windows 10 1607, Microsoft Windows 10 1703, Microsoft Windows 10 1709, Microsoft Windows 10 1803, Microsoft Windows 10 1809, Microsoft Windows 7, Microsoft Windows 8.1, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019.

## How do I fix CVE-2018-8611?

No fix has been published for CVE-2018-8611 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 14 Jun 2022.

## Is CVE-2018-8611 being exploited?

Yes. Attackers have exploited CVE-2018-8611 in the wild since at least 24 May 2022.

Public exploit code:

- https://github.com/lsw29475/CVE-2018-8611 (github_poc): https://github.com/lsw29475/CVE-2018-8611
- CVE-2018-8611 PrivEsc Exploit (github_poc): https://github.com/ahm3dgg/cve-2018-8611

## Other vulnerabilities in Microsoft Windows 10 1607

- [CVE-2026-33824](https://insights.sbomify.com/CVE-2026-33824/): Microsoft Internet Key Exchange (IKE) Service Extensions Double Free (critical 9.8, exploited in the wild)
- [CVE-2026-21510](https://insights.sbomify.com/CVE-2026-21510/): Microsoft Windows Shell Protection Mechanism Failure (high 8.8, exploited in the wild)
- [CVE-2026-21513](https://insights.sbomify.com/CVE-2026-21513/): Microsoft MSHTML Framework Protection Mechanism Failure (high 8.8, exploited in the wild)
- [CVE-2023-32049](https://insights.sbomify.com/CVE-2023-32049/): Microsoft Windows Defender SmartScreen Security Feature Bypass (high 8.8, exploited in the wild)
- [CVE-2023-29360](https://insights.sbomify.com/CVE-2023-29360/): Microsoft Streaming Service Untrusted Pointer Dereference (high 8.4, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-8611 and fix it if it is affected.

What it is: CVE-2018-8611 is a high-severity vulnerability in Microsoft Windows 10 1607, published on 12 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2018-8611 in the wild since at least 24 May 2022.

Affected product: Microsoft Windows 10 1607. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-8611/ (Markdown: https://insights.sbomify.com/CVE-2018-8611/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-8611
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-8611
- OSV: https://osv.dev/vulnerability/CVE-2018-8611

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-8611/
Summaries are generated and may contain mistakes; the official description above is the record.