# CVE-2016-7255: Microsoft Win32k Privilege Escalation

> Local attackers can gain elevated privileges on Windows systems by exploiting a vulnerability in kernel-mode drivers via a crafted application.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 3 Nov 2021 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 10 Nov 2016
- **Updated:** 10 Sep 2026
- **Also known as:** GHSA-6rfx-wjcx-jvgf

## What is CVE-2016-7255?

CVE-2016-7255 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 10 Nov 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

The kernel-mode drivers in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT 8.1, Windows 10 Gold, 1511, and 1607, and Windows Server 2016 allow local users to gain privileges via a crafted application, aka "Win32k Elevation of Privilege Vulnerability."

## Which versions are affected by CVE-2016-7255?

It affects 10 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1511, Microsoft Windows 10 1607, 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 Vista.

## How do I fix CVE-2016-7255?

No fix has been published for CVE-2016-7255 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 3 May 2022.

## Is CVE-2016-7255 being exploited?

Yes. Attackers have exploited CVE-2016-7255 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

Public exploit code:

- An exploit for CVE-2016-7255 on Windows 7/8/8.1/10(pre-anniversary) 64 bit (github_poc): https://github.com/FSecureLABS/CVE-2016-7255
- A demonstration of how page tables can be used to run arbitrary code in ring-0 and lead to a privesc. Uses CVE-2016-7255 as an example. (github_poc): https://github.com/yuvatia/page-table-exploitation
- https://github.com/heh3/CVE-2016-7255 (github_poc): https://github.com/heh3/CVE-2016-7255
- porting CVE-2016-7255 to x86 for educational purposes. (github_poc): https://github.com/bbolmin/cve-2016-7255_x86_x64
- Microsoft Windows Kernel - 'win32k' Denial of Service (MS16-135) (exploitdb)
- Microsoft Windows Kernel - 'win32k.sys NtSetWindowLongPtr' Local Privilege Escalation (MS16-135) (1) (exploitdb)

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-7255 and fix it if it is affected.

What it is: CVE-2016-7255 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 10 Nov 2016. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: Yes. Attackers have exploited CVE-2016-7255 in the wild since at least 3 Nov 2021, including in ransomware campaigns.

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

## Sources

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

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