# CVE-2025-24043: WinDbg Remote Code Execution Vulnerability

> An authorized attacker can execute arbitrary code over the network due to improper cryptographic signature verification in WinDbg.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Mar 2025
- **Updated:** 13 Feb 2026
- **Also known as:** GHSA-hpw7-8qpc-34p3

## What is CVE-2025-24043?

CVE-2025-24043 is a high-severity code injection vulnerability in Microsoft WinDbg, published on 11 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Improper verification of cryptographic signature in .NET allows an authorized attacker to execute code over a network.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2025-24043?

6 open source packages ship an affected version, including dotnet-debugger-extensions, dotnet-dump and dotnet-sos. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dotnet-debugger-extensions` | NuGet | All versions | 9.0.607601 |
| `dotnet-debugger-extensions` | NuGet | All versions | 9.0.607601 |
| `dotnet-dump` | NuGet | All versions | 9.0.607501 |
| `dotnet-dump` | NuGet | All versions | 9.0.607501 |
| `dotnet-sos` | NuGet | All versions | 9.0.607501 |
| `dotnet-sos` | NuGet | All versions | 9.0.607501 |

Products: Microsoft Windbg.

## How do I fix CVE-2025-24043?

Upgrade dotnet-debugger-extensions to 9.0.607601 or later.

## Is CVE-2025-24043 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-24043 and fix it if it is affected.

What it is: CVE-2025-24043 is a high-severity code injection vulnerability in Microsoft WinDbg, published on 11 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-24043 in the wild and no public exploit code.

Affected packages and fixed versions:
- dotnet-debugger-extensions (NuGet): affected all versions; fixed in 9.0.607601
- dotnet-debugger-extensions (NuGet): affected all versions; fixed in 9.0.607601
- dotnet-dump (NuGet): affected all versions; fixed in 9.0.607501
- dotnet-dump (NuGet): affected all versions; fixed in 9.0.607501
- dotnet-sos (NuGet): affected all versions; fixed in 9.0.607501
- dotnet-sos (NuGet): affected all versions; fixed in 9.0.607501

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

## Sources

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

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