# CVE-2018-8120: Microsoft Win32k Privilege Escalation

> Attackers can exploit a Win32k memory handling flaw to gain elevated privileges on affected Windows systems.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 15 Mar 2022 (CISA KEV), used in ransomware
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 May 2018
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-v82r-2hh9-72g8

## What is CVE-2018-8120?

CVE-2018-8120 is a high-severity vulnerability in Microsoft Windows 7, published on 9 May 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 in Windows when the Win32k component fails to properly handle objects in memory, aka "Win32k Elevation of Privilege Vulnerability." This affects Windows Server 2008, Windows 7, Windows Server 2008 R2. This CVE ID is unique from CVE-2018-8124, CVE-2018-8164, CVE-2018-8166.

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

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

It affects 2 products.


Products: Microsoft Windows 7, Microsoft Windows Server 2008.

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

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

## Is CVE-2018-8120 being exploited?

Yes. Attackers have exploited CVE-2018-8120 in the wild since at least 15 Mar 2022, including in ransomware campaigns.

Public exploit code:

- CVE-2018-8120 Windows LPE exploit (github_poc): https://github.com/rip1s/CVE-2018-8120
- CVE-2018-8120 Exploit for Win2003 Win2008 WinXP Win7  (github_poc): https://github.com/alpha1ab/CVE-2018-8120
- https://github.com/bigric3/cve-2018-8120 (github_poc): https://github.com/bigric3/cve-2018-8120
- https://github.com/ne1llee/cve-2018-8120 (github_poc): https://github.com/ne1llee/cve-2018-8120
- dd (github_poc): https://github.com/EVOL4/CVE-2018-8120
- CVE-2018-8120 Windows LPE exploit (github_poc): https://github.com/ozkanbilge/CVE-2018-8120

## Other vulnerabilities in Microsoft Windows 7

- [CVE-2015-1635](https://insights.sbomify.com/CVE-2015-1635/): Microsoft HTTP.sys Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-2360](https://insights.sbomify.com/CVE-2015-2360/): Microsoft Win32k Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6324](https://insights.sbomify.com/CVE-2014-6324/): Microsoft Kerberos Key Distribution Center (KDC) Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6332](https://insights.sbomify.com/CVE-2014-6332/): Microsoft Windows Object Linking & Embedding (OLE) Automation Array Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2014-4148](https://insights.sbomify.com/CVE-2014-4148/): Microsoft Windows Remote Code Execution (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-8120 is a high-severity vulnerability in Microsoft Windows 7, published on 9 May 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-8120 in the wild since at least 15 Mar 2022, including in ransomware campaigns.

Affected product: Microsoft Windows 7. 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-8120/ (Markdown: https://insights.sbomify.com/CVE-2018-8120/index.md)
```

## Sources

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

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