How severe is CVE-2025-21172?

CVE-2025-21172 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by CVE-2025-21172?

CVE-2025-21172 affects the following packages: Microsoft.NetCore.App.Runtime.linux-arm (NuGet), Microsoft.NetCore.App.Runtime.linux-arm64 (NuGet), Microsoft.NetCore.App.Runtime.linux-musl-arm (NuGet), Microsoft.NetCore.App.Runtime.linux-musl-arm64 (NuGet), Microsoft.NetCore.App.Runtime.linux-musl-x64 (NuGet), Microsoft.NetCore.App.Runtime.linux-x64 (NuGet), Microsoft.NetCore.App.Runtime.osx-arm64 (NuGet), Microsoft.NetCore.App.Runtime.osx-x64 (NuGet), and 15 more. Ecosystems affected: NuGet.

How do I fix CVE-2025-21172?

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 CVE-2025-21172 is resolved across your whole dependency graph.

How do I detect CVE-2025-21172 in my NuGet dependencies?

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.

How do I mitigate CVE-2025-21172 if there is no patch (or I can't update yet)?

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.

How does O3 Security protect against CVE-2025-21172?

O3 pinpoints whether CVE-2025-21172 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is CVE-2025-21172 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-21172 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-21172?

CVE-2025-21172 has an EPSS (Exploit Prediction Scoring System) score of 1.8%, placing it in the 75th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-21172?

CVE-2025-21172 is classified as CWE-122 (CWE-122), CWE-190 (CWE-190). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-21172 published, and has it been updated?

CVE-2025-21172 was published on January 14, 2025 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

.NET NuGet

CVE-2025-21172

HIGH

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

Also known asBIT-dotnet-2025-21172BIT-dotnet-sdk-2025-21172GHSA-jjcv-wr2g-4rv4

Published

Jan 14, 2025

Updated

Apr 10, 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%

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

.NET and Visual Studio Remote Code Execution Vulnerability

Affected Packages

23 total 23 fixed

Ecosystem	Package	Vulnerable range	Fix
.NETNuGet	`Microsoft.NetCore.App.Runtime.linux-arm`	≥ 9.0.0&&< 9.0.1	9.0.1
.NETNuGet	`Microsoft.NetCore.App.Runtime.linux-arm64`	≥ 9.0.0&&< 9.0.1	9.0.1
.NETNuGet	`Microsoft.NetCore.App.Runtime.linux-musl-arm`	≥ 9.0.0&&< 9.0.1	9.0.1
.NETNuGet	`Microsoft.NetCore.App.Runtime.linux-musl-arm64`	≥ 9.0.0&&< 9.0.1	9.0.1
.NETNuGet	`Microsoft.NetCore.App.Runtime.linux-musl-x64`	≥ 9.0.0&&< 9.0.1	9.0.1
.NETNuGet	`Microsoft.NetCore.App.Runtime.linux-x64`	≥ 9.0.0&&< 9.0.1	9.0.1

Detection & mitigation playbook

Open-source dependency

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.
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 CVE-2025-21172 is resolved across your whole dependency graph.
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.
How O3 protects you
O3 pinpoints whether CVE-2025-21172 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 CVE-2025-21172. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

.NET and Visual Studio Remote Code Execution Vulnerability

O3 Security · Impact-Aware SCA

Is CVE-2025-21172 in your dependencies?

O3 detects CVE-2025-21172 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works