# CVE-2015-2546: Microsoft Win32k Memory Corruption

> Local attackers can gain elevated privileges via a crafted application exploiting a memory corruption flaw in the Windows kernel-mode driver.

- **Severity:** High 8.2 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Sep 2015
- **Updated:** 14 Aug 2026
- **Also known as:** GHSA-5c8h-c2cj-96mm

## What is CVE-2015-2546?

CVE-2015-2546 is a high-severity memory corruption vulnerability in Microsoft Windows 10 1507, published on 9 Sep 2015. 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 driver in Microsoft Windows Vista SP2, Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8, Windows 8.1, Windows Server 2012 Gold and R2, Windows RT Gold and 8.1, and Windows 10 allows local users to gain privileges via a crafted application, aka "Win32k Memory Corruption Elevation of Privilege Vulnerability," a different vulnerability than CVE-2015-2511, CVE-2015-2517, and CVE-2015-2518.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2015-2546?

It affects 9 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 7, Microsoft Windows 8, Microsoft Windows 8.1, Microsoft Windows Rt, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Vista.

## How do I fix CVE-2015-2546?

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

## Is CVE-2015-2546 being exploited?

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

Public exploit code:

- https://github.com/k0keoyo/CVE-2015-2546-Exploit (github_poc): https://github.com/k0keoyo/CVE-2015-2546-Exploit

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

What it is: CVE-2015-2546 is a high-severity memory corruption vulnerability in Microsoft Windows 10 1507, published on 9 Sep 2015. 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-2015-2546 in the wild since at least 15 Mar 2022, 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-2015-2546/ (Markdown: https://insights.sbomify.com/CVE-2015-2546/index.md)
```

## Sources

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

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