# CVE-2026-32175: .NET Core Tampering Vulnerability > An attacker can write arbitrary files to limited locations on a system by sending a specially crafted file to the .NET Core runtime. - **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N/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:** 12 May 2026 - **Updated:** 10 Aug 2026 - **Also known as:** BELL-CVE-2026-32175, BIT-dotnet-2026-32175, BIT-dotnet-sdk-2026-32175, GHSA-rg75-q538-x34v, MINI-87r8-jwjx-3whx, MINI-j55f-j6xx-7hcv, UBUNTU-CVE-2026-32175 ## What is CVE-2026-32175? CVE-2026-32175 is a medium-severity path traversal vulnerability in Microsoft .Net, published on 12 May 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory), CWE-36 (Absolute Path Traversal) ## Which versions are affected by CVE-2026-32175? 26 open source packages ship an affected version, including Microsoft.NetCore.App.Runtime.win-arm, dotnet and dotnet-sdk. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `Microsoft.NetCore.App.Runtime.win-arm` | NuGet | From 10.0.0 | 10.0.8 | | `Microsoft.NetCore.App.Runtime.win-arm` | NuGet | From 10.0.0 | 10.0.8 | | `Microsoft.NetCore.App.Runtime.win-arm` | NuGet | From 8.0.0 | 8.0.27 | | `Microsoft.NetCore.App.Runtime.win-arm` | NuGet | From 8.0.0 | 8.0.27 | | `Microsoft.NetCore.App.Runtime.win-arm` | NuGet | From 9.0.0 | 9.0.16 | | `Microsoft.NetCore.App.Runtime.win-arm` | NuGet | From 9.0.0 | 9.0.16 | | `dotnet` | Bitnami | From 8.0.0 | 8.0.27, 9.0.16 | | `dotnet-sdk` | Bitnami | From 8.0.0 | 8.0.27, 9.0.16 | | `Microsoft.NetCore.App.Runtime.win-arm64` | NuGet | From 10.0.0 | 10.0.8 | | `Microsoft.NetCore.App.Runtime.win-arm64` | NuGet | From 10.0.0 | 10.0.8 | | `Microsoft.NetCore.App.Runtime.win-arm64` | NuGet | From 8.0.0 | 8.0.27 | | `Microsoft.NetCore.App.Runtime.win-arm64` | NuGet | From 8.0.0 | 8.0.27 | | `Microsoft.NetCore.App.Runtime.win-arm64` | NuGet | From 9.0.0 | 9.0.16 | | `Microsoft.NetCore.App.Runtime.win-arm64` | NuGet | From 9.0.0 | 9.0.16 | | `Microsoft.NetCore.App.Runtime.win-x64` | NuGet | From 10.0.0 | 10.0.8 | | `Microsoft.NetCore.App.Runtime.win-x64` | NuGet | From 10.0.0 | 10.0.8 | | `Microsoft.NetCore.App.Runtime.win-x64` | NuGet | From 8.0.0 | 8.0.27 | | `Microsoft.NetCore.App.Runtime.win-x64` | NuGet | From 8.0.0 | 8.0.27 | | `Microsoft.NetCore.App.Runtime.win-x64` | NuGet | From 9.0.0 | 9.0.16 | | `Microsoft.NetCore.App.Runtime.win-x64` | NuGet | From 9.0.0 | 9.0.16 | | `Microsoft.NetCore.App.Runtime.win-x86` | NuGet | From 10.0.0 | 10.0.8 | | `Microsoft.NetCore.App.Runtime.win-x86` | NuGet | From 10.0.0 | 10.0.8 | | `Microsoft.NetCore.App.Runtime.win-x86` | NuGet | From 8.0.0 | 8.0.27 | | `Microsoft.NetCore.App.Runtime.win-x86` | NuGet | From 8.0.0 | 8.0.27 | | `Microsoft.NetCore.App.Runtime.win-x86` | NuGet | From 9.0.0 | 9.0.16 | | `Microsoft.NetCore.App.Runtime.win-x86` | NuGet | From 9.0.0 | 9.0.16 | Products: Microsoft .Net, Microsoft Visual Studio 2022, Microsoft Visual Studio 2026. ## How do I fix CVE-2026-32175? Upgrade Microsoft.NetCore.App.Runtime.win-arm to a fixed version for your release line: 10.0.8, 8.0.27 or 9.0.16. ## Is CVE-2026-32175 being exploited? There is no known exploitation of CVE-2026-32175 in the wild and no public exploit code. ## Other vulnerabilities in Microsoft .Net - [CVE-2024-43498](https://insights.sbomify.com/CVE-2024-43498/): .NET and Visual Studio Remote Code Execution Vulnerability (critical 9.8) - [CVE-2024-0057](https://insights.sbomify.com/CVE-2024-0057/): NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability (critical 9.1) - [CVE-2026-96957](https://insights.sbomify.com/CVE-2026-96957/): .NET Security Feature Bypass Vulnerability (high 8.8) - [CVE-2026-69439](https://insights.sbomify.com/CVE-2026-69439/): .NET and Visual Studio Elevation of Privilege Vulnerability (high 8.8) - [CVE-2026-71328](https://insights.sbomify.com/CVE-2026-71328/): .NET and Visual Studio Remote Code Execution Vulnerability (high 8.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-32175 and fix it if it is affected. What it is: CVE-2026-32175 is a medium-severity path traversal vulnerability in Microsoft .Net, published on 12 May 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-32175 in the wild and no public exploit code. Affected packages and fixed versions: - Microsoft.NetCore.App.Runtime.win-arm (NuGet): affected from 10.0.0; fixed in 10.0.8 - Microsoft.NetCore.App.Runtime.win-arm (NuGet): affected from 10.0.0; fixed in 10.0.8 - Microsoft.NetCore.App.Runtime.win-arm (NuGet): affected from 8.0.0; fixed in 8.0.27 - Microsoft.NetCore.App.Runtime.win-arm (NuGet): affected from 8.0.0; fixed in 8.0.27 - Microsoft.NetCore.App.Runtime.win-arm (NuGet): affected from 9.0.0; fixed in 9.0.16 - Microsoft.NetCore.App.Runtime.win-arm (NuGet): affected from 9.0.0; fixed in 9.0.16 - dotnet (Bitnami): affected from 8.0.0; fixed in 8.0.27, 9.0.16 - dotnet-sdk (Bitnami): affected from 8.0.0; fixed in 8.0.27, 9.0.16 - Microsoft.NetCore.App.Runtime.win-arm64 (NuGet): affected from 10.0.0; fixed in 10.0.8 - Microsoft.NetCore.App.Runtime.win-arm64 (NuGet): affected from 10.0.0; fixed in 10.0.8 - Microsoft.NetCore.App.Runtime.win-arm64 (NuGet): affected from 8.0.0; fixed in 8.0.27 - Microsoft.NetCore.App.Runtime.win-arm64 (NuGet): affected from 8.0.0; fixed in 8.0.27 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-2026-32175/ (Markdown: https://insights.sbomify.com/CVE-2026-32175/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32175 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32175 - OSV: https://osv.dev/vulnerability/CVE-2026-32175 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-32175/ Summaries are generated and may contain mistakes; the official description above is the record.