# CVE-2017-0263: Microsoft Win32k Privilege Escalation

> Local attackers can gain elevated privileges on Microsoft Windows systems by exploiting a use-after-free flaw in kernel-mode drivers via a crafted application.

- **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 10 Feb 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 May 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-c264-rp8f-rf64

## What is CVE-2017-0263?

CVE-2017-0263 is a high-severity use after free vulnerability in Microsoft Windows 10 1507, published on 12 May 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The kernel-mode drivers in Microsoft 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, 1607, 1703, and Windows Server 2016 allow local users to gain privileges via a crafted application, aka "Win32k Elevation of Privilege Vulnerability."

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2017-0263?

It affects 10 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1511, Microsoft Windows 10 1607, Microsoft Windows 10 1703, Microsoft Windows 7, Microsoft Windows 8.1, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016.

## How do I fix CVE-2017-0263?

No fix has been published for CVE-2017-0263 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 10 Aug 2022.

## Is CVE-2017-0263 being exploited?

Yes. Attackers have exploited CVE-2017-0263 in the wild since at least 10 Feb 2022.

Public exploit code:

- Microsoft Windows Manager (7 x86) - Menu Management Component UAF Privilege Elevation (exploitdb)
- poc for 0263 (github_poc): https://github.com/R06otMD5/cve-2017-0263-poc

## 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-2017-0263 and fix it if it is affected.

What it is: CVE-2017-0263 is a high-severity use after free vulnerability in Microsoft Windows 10 1507, published on 12 May 2017. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-0263 in the wild since at least 10 Feb 2022.

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-2017-0263/ (Markdown: https://insights.sbomify.com/CVE-2017-0263/index.md)
```

## Sources

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

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