Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
.NET NuGet

GHSA-jjcv-wr2g-4rv4

HIGH

Microsoft Security Advisory CVE-2025-21172 | .NET and Visual Studio Remote Code Execution Vulnerability

Also known asBIT-dotnet-2025-21172BIT-dotnet-sdk-2025-21172CVE-2025-21172
Published
Jan 14, 2025
Updated
Feb 4, 2026
Affected
23 pkgs
Patched
23 / 23
Exploits
None indexed

EPSS Exploitation Probability

via FIRST.org ↗
1.8%probability of exploitation in next 30 days
Lower Risk75th percentile+1.33%
0.00%0.75%1.51%2.26%0.4%1.8%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

23 pkgs affected
.NETMicrosoft.NetCore.App.Runtime.linux-arm.NETMicrosoft.NetCore.App.Runtime.linux-arm64.NETMicrosoft.NetCore.App.Runtime.linux-musl-arm.NETMicrosoft.NetCore.App.Runtime.linux-musl-arm64.NETMicrosoft.NetCore.App.Runtime.linux-musl-x64.NETMicrosoft.NetCore.App.Runtime.linux-x64.NETMicrosoft.NetCore.App.Runtime.osx-arm64.NETMicrosoft.NetCore.App.Runtime.osx-x64+15 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects NuGet packages — download data is not available via public APIs for these ecosystems.

Description

Microsoft Security Advisory CVE-2025-21172 | .NET and Visual Studio Remote Code Execution Vulnerability

<a name="executive-summary"></a>Executive summary

Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 8.0 and .NET 9.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.

An attacker could exploit this vulnerability by loading a specially crafted file in Visual Studio.

Announcement

Announcement for this issue can be found at https://github.com/dotnet/runtime/issues/111424.

<a name="mitigation-factors"></a>Mitigation factors

Microsoft has not identified any mitigating factors for this vulnerability.

<a name="affected-software"></a>Affected software

  • Any .NET 8.0 application running on .NET 8.0.11 or earlier.
  • Any .NET 9.0 application running on .NET 9.0.0 or earlier.

<a name="affected-packages"></a>Affected Packages

The vulnerability affects any Microsoft .NET project if it uses any of affected packages versions listed below

<a name=".NET 9"></a>.NET 9

<a name=".NET 8"></a>.NET 8

Package nameAffected versionPatched version
Microsoft.NetCore.App.Runtime.linux-arm>= 8.0.0, < 8.0.128.0.12
Microsoft.NetCore.App.Runtime.linux-arm64>= 8.0.0, < 8.0.128.0.12
Microsoft.NetCore.App.Runtime.linux-musl-arm>= 8.0.0, < 8.0.128.0.12
Microsoft.NetCore.App.Runtime.linux-musl-arm64>= 8.0.0, < 8.0.128.0.12
Microsoft.NetCore.App.Runtime.linux-musl-x64>= 8.0.0, < 8.0.128.0.12
Microsoft.NetCore.App.Runtime.linux-x64>= 8.0.0, < 8.0.128.0.12
Microsoft.NetCore.App.Runtime.osx-arm64>= 8.0.0, < 8.0.128.0.12
Microsoft.NetCore.App.Runtime.osx-x64>= 8.0.0, < 8.0.128.0.12
Microsoft.NetCore.App.Runtime.win-arm>= 8.0.0, < 8.0.128.0.12
Microsoft.NetCore.App.Runtime.win-arm64>= 8.0.0, < 8.0.128.0.12
Microsoft.NetCore.App.Runtime.win-x64>= 8.0.0, < 8.0.128.0.12
Microsoft.NetCore.App.Runtime.win-x86>= 8.0.0, < 8.0.128.0.12

Advisory FAQ

<a name="how-affected"></a>How do I know if I am affected?

If you have a runtime or SDK with a version listed, or an affected package listed in affected software or affected packages, you're exposed to the vulnerability.

<a name="how-fix"></a>How do I fix the issue?

  1. To fix the issue please install the latest version of .NET 8.0 or .NET 9.0, as appropriate. If you have installed one or more .NET SDKs through Visual Studio, Visual Studio will prompt you to update Visual Studio, which will also update your .NET SDKs.
  2. If your application references the vulnerable package, update the package reference to the patched version.
  • You can list the versions you have installed by running the dotnet --info command. You will see output like the following;
.NET SDK:
 Version:           9.0.100
 Commit:            59db016f11
 Workload version:  9.0.100-manifests.3068a692
 MSBuild version:   17.12.7+5b8665660

Runtime Environment:
 OS Name:     Mac OS X
 OS Version:  15.2
 OS Platform: Darwin
 RID:         osx-arm64
 Base Path:   /usr/local/share/dotnet/sdk/9.0.100/

.NET workloads installed:
There are no installed workloads to display.
Configured to use loose manifests when installing new manifests.

Host:
  Version:      9.0.0
  Architecture: arm64
  Commit:       9d5a6a9aa4

.NET SDKs installed:
  9.0.100 [/usr/local/share/dotnet/sdk]

.NET runtimes installed:
  Microsoft.AspNetCore.App 9.0.0 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
  Microsoft.NETCore.App 9.0.0 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]

Other architectures found:
  x64   [/usr/local/share/dotnet]
    registered at [/etc/dotnet/install_location_x64]

Environment variables:
  Not set

global.json file:
  Not found

Learn more:
  https://aka.ms/dotnet/info

Download .NET:
  https://aka.ms/dotnet/download

Once you have installed the updated runtime or SDK, restart your apps for the update to take effect.

Additionally, if you've deployed self-contained applications targeting any of the impacted versions, these applications are also vulnerable and must be recompiled and redeployed.

Other Information

Reporting Security Issues

If you have found a potential security issue in .NET 8.0 or .NET 9.0, please email details to [email protected]. Reports may qualify for the Microsoft .NET Core & .NET 5 Bounty. Details of the Microsoft .NET Bounty Program including terms and conditions are at https://aka.ms/corebounty.

Support

You can ask questions about this issue on GitHub in the .NET GitHub organization. The main repos are located at https://github.com/dotnet/runtime. The Announcements repo (https://github.com/dotnet/Announcements) will contain this bulletin as an issue and will include a link to a discussion issue. You can ask questions in the linked discussion issue.

Disclaimer

The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.

External Links

CVE-2025-21172

Revisions

V1.0 (January 14, 2024): Advisory published.

Affected Packages

23 total 23 fixed
EcosystemPackageVulnerable rangeFix
.NETNuGetMicrosoft.NetCore.App.Runtime.linux-arm9.0.0&&< 9.0.19.0.1
.NETNuGetMicrosoft.NetCore.App.Runtime.linux-arm649.0.0&&< 9.0.19.0.1
.NETNuGetMicrosoft.NetCore.App.Runtime.linux-musl-arm9.0.0&&< 9.0.19.0.1
.NETNuGetMicrosoft.NetCore.App.Runtime.linux-musl-arm649.0.0&&< 9.0.19.0.1
.NETNuGetMicrosoft.NetCore.App.Runtime.linux-musl-x649.0.0&&< 9.0.19.0.1
.NETNuGetMicrosoft.NetCore.App.Runtime.linux-x649.0.0&&< 9.0.19.0.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.NetCore.App.Runtime.linux-arm. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update Microsoft.NetCore.App.Runtime.linux-arm to 9.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jjcv-wr2g-4rv4 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-jjcv-wr2g-4rv4 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-jjcv-wr2g-4rv4. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

# Microsoft Security Advisory CVE-2025-21172 | .NET and Visual Studio Remote Code Execution Vulnerability ## <a name="executive-summary"></a>Executive summary Microsoft is releasing this security advisory to provide information about a vulnerability in .NET 8.0 and .NET 9.0. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability. An attacker could exploit this vulnerability by loading a specially crafted file in Visual Studio. ## Announcement Announcement for this issue can be found at https://github.com/dotnet/runtime/issu
O3 Security · Impact-Aware SCA

Is GHSA-jjcv-wr2g-4rv4 in your dependencies?

O3 detects GHSA-jjcv-wr2g-4rv4 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.