Is dotnet-dump 3.1 vulnerable?
NuGet · 6 releases from 3.1.57502 to 3.1.141901 · latest dotnet-dump is 10.0.750501 · checked 18 Nov 2026
Yes: 1 known advisory
Yes. dotnet-dump 3.1.141901, the last 3.1 release, is affected by 1 known security advisory (1 high), including CVE-2025-24043. Upgrade to 9.0.607501 or later to fix all of them.
dotnet add package dotnet-dump --version 9.0.607501Is your project on an affected dotnet-dump?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting dotnet-dump 3.1.141901
Microsoft Security Advisory CVE-2025-24043 | WinDbg Remote Code Execution Vulnerability
- Affected
- <9.0.607501
- Fixed in
- 9.0.607501
Every dotnet-dump 3.1.x release
Affected: 3.1.57502 to 3.1.141901. Latest dotnet-dump: 10.0.750501.
| Version | Known advisories |
|---|---|
| dotnet-dump 3.1.141901 | CVE-2025-24043 |
| dotnet-dump 3.1.137102 | CVE-2025-24043 |
| dotnet-dump 3.1.135903 | CVE-2025-24043 |
| dotnet-dump 3.1.122203 | CVE-2025-24043 |
| dotnet-dump 3.1.120604 | CVE-2025-24043 |
| dotnet-dump 3.1.57502 | CVE-2025-24043 |
Which of your client projects are still on dotnet-dump 3.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact dotnet-dump version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other dotnet-dump versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.