CVE-2026-32175
MEDIUMCVE-2026-32175 is a medium-severity (CVSS 4.3) CWE-36 vulnerability in Microsoft.NetCore.App.Runtime.win-arm. O3 Security confirms whether CVE-2026-32175 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Microsoft Security Advisory CVE-2026-32175 – .NET Core Tampering Vulnerability
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-32175.
EPSS Exploitation Probability
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.
How urgent is this, really
CVE-2026-32175 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 360,142 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
Microsoft.NetCore.App.Runtime.win-arm.NETMicrosoft.NetCore.App.Runtime.win-arm.NETMicrosoft.NetCore.App.Runtime.win-arm.NETMicrosoft.NetCore.App.Runtime.win-arm64.NETMicrosoft.NetCore.App.Runtime.win-arm64.NETMicrosoft.NetCore.App.Runtime.win-arm64.NETMicrosoft.NetCore.App.Runtime.win-x64.NETMicrosoft.NetCore.App.Runtime.win-x64+4 moreReal-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
A tampering vulnerability exists when .NET Core improperly handles specially crafted files. An attacker who successfully exploited this vulnerability could write arbitrary files and directories to certain locations on a vulnerable system. However, an attacker would have limited control over the destination of the files and directories. To exploit the vulnerability, an attacker must send a specially crafted file to a vulnerable system. The security update fixes the vulnerability by ensuring .NET Core properly handles files.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| .NETNuGet | Microsoft.NetCore.App.Runtime.win-arm | ≥ 8.0.0&&< 8.0.27 | 8.0.27 |
| .NETNuGet | Microsoft.NetCore.App.Runtime.win-arm | ≥ 9.0.0&&< 9.0.16 | 9.0.16 |
| .NETNuGet | Microsoft.NetCore.App.Runtime.win-arm | ≥ 10.0.0&&< 10.0.8 | 10.0.8 |
| .NETNuGet | Microsoft.NetCore.App.Runtime.win-arm64 | ≥ 8.0.0&&< 8.0.27 | 8.0.27 |
| .NETNuGet | Microsoft.NetCore.App.Runtime.win-arm64 | ≥ 9.0.0&&< 9.0.16 | 9.0.16 |
| .NETNuGet | Microsoft.NetCore.App.Runtime.win-arm64 | ≥ 10.0.0&&< 10.0.8 | 10.0.8 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for Microsoft.NetCore.App.Runtime.win-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.win-arm to 8.0.27 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32175 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-2026-32175 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-2026-32175. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-32175 in your dependencies?
O3 detects CVE-2026-32175 across NuGet dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.