# CVE-2024-43491: Microsoft Windows Update Remote Code Execution Vulnerability

> An attacker can execute arbitrary code on Windows 10 LTSB systems by exploiting a use-after-free vulnerability in the Servicing Stack that reverted previous security fixes.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H/E:F/RL:O/RC:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Sep 2024
- **Updated:** 10 Aug 2026
- **Also known as:** GHSA-m882-rgxp-c7jh

## What is CVE-2024-43491?

CVE-2024-43491 is a critical use after free vulnerability in Microsoft Windows 10 1507, published on 10 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Microsoft is aware of a vulnerability in Servicing Stack that has rolled back the fixes for some vulnerabilities affecting Optional Components on Windows 10, version 1507 (initial version released July 2015). This means that an attacker could exploit these previously mitigated vulnerabilities on Windows 10, version 1507 (Windows 10 Enterprise 2015 LTSB and Windows 10 IoT Enterprise 2015 LTSB) systems that have installed the Windows security update released on March 12, 2024—KB5035858 (OS Build 10240.20526) or other updates released until August 2024. All later versions of Windows 10 are not impacted by this vulnerability.
This servicing stack vulnerability is addressed by installing the September 2024 Servicing stack update (SSU KB5043936) AND the September 2024 Windows security update (KB5043083), in that order.
Note: Windows 10, version 1507 reached the end of support (EOS) on May 9, 2017 for devices running the Pro, Home, Enterprise, Education, and Enterprise IoT editions. Only Windows 10 Enterprise 2015 LTSB and Windows 10 IoT Enterprise 2015 LTSB editions are still under support.

Weakness: CWE-416 (Use After Free)

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

It affects 1 product.


Products: Microsoft Windows 10 1507.

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

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

## Is CVE-2024-43491 being exploited?

There is no known exploitation of CVE-2024-43491 in the wild and no public exploit code.

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

What it is: CVE-2024-43491 is a critical use after free vulnerability in Microsoft Windows 10 1507, published on 10 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-43491 in the wild and no public exploit code.

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

## Sources

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

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