# CVE-2024-26229: Windows CSC Service Elevation of Privilege Vulnerability

> An attacker can exploit a heap-based buffer overflow in the Windows CSC Service to gain elevated 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/E:U/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2024
- **Updated:** 3 May 2025
- **Also known as:** GHSA-m3pg-c9mv-657r

## What is CVE-2024-26229?

CVE-2024-26229 is a high-severity memory corruption vulnerability in Microsoft Windows 10 1507, published on 9 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Windows CSC Service Elevation of Privilege Vulnerability

Weakness: CWE-122 (Heap-based Buffer Overflow)

## Which versions are affected by CVE-2024-26229?

It affects 14 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1607, Microsoft Windows 10 1809, Microsoft Windows 10 21h2, Microsoft Windows 10 22h2, Microsoft Windows 11 21h2, Microsoft Windows 11 22h2, Microsoft Windows 11 23h2, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Server 2019, Microsoft Windows Server 2022, Microsoft Windows Server 2022 23h2.

## How do I fix CVE-2024-26229?

No fix has been published for CVE-2024-26229 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-26229 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-26229 exists.

Public exploit code:

- Windows LPE (github_poc): https://github.com/RalfHacker/CVE-2024-26229-exploit
- A firebeam plugin that exploits the CVE-2024-26229 vulnerability to perform elevation of privilege from a  unprivileged user (github_poc): https://github.com/Cracked5pider/eop24-26229
- BOF implementations of CVE-2024-26229 for Cobalt Strike and BruteRatel (github_poc): https://github.com/apkc/CVE-2024-26229-BOF
- Windows CSC服务特权提升漏洞。  当程序向缓冲区写入的数据超出其处理能力时，就会发生基于堆的缓冲区溢出，从而导致多余的数据溢出到相邻的内存区域。这种溢出会损坏内存，并可能使攻击者能够执行任意代码或未经授权访问系统。本质上，攻击者可以编写触发溢出的恶意代码或输入，从而控制受影响的系统、执行任意命令、安装恶意软件或访问敏感数据。  微软已发出警告成功利用此漏洞的攻击者可以获得 SYSTEM 权限，这是 Windows 系统上的最高访问级别。这增加了与 CVE-2024-26229 相关的风险，使其成为恶意行为者的主要目标。 (github_poc): https://github.com/team-MineDEV/CVE-2024-26229
- CWE-781: Improper Address Validation in IOCTL with METHOD_NEITHER I/O Control Code (github_poc): https://github.com/dkstar11q/CVE-2024-26229-lpe
- https://github.com/mqxmm/CVE-2024-26229 (github_poc): https://github.com/mqxmm/CVE-2024-26229

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

What it is: CVE-2024-26229 is a high-severity memory corruption vulnerability in Microsoft Windows 10 1507, published on 9 Apr 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-26229 exists.

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

## Sources

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

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