CVE-2026-32175 .NET Core Tampering Vulnerability

Medium 4.3 Published Updated

An attacker can write arbitrary files to limited locations on a system by sending a specially crafted file to the .NET Core runtime.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

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, CWE-36

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.

PackageAffectedFixed in
Microsoft.NetCore.App.Runtime.win-arm NuGetFrom 10.0.010.0.8
Microsoft.NetCore.App.Runtime.win-arm NuGetFrom 10.0.010.0.8
Microsoft.NetCore.App.Runtime.win-arm NuGetFrom 8.0.08.0.27
Microsoft.NetCore.App.Runtime.win-arm NuGetFrom 8.0.08.0.27
Microsoft.NetCore.App.Runtime.win-arm NuGetFrom 9.0.09.0.16
Microsoft.NetCore.App.Runtime.win-arm NuGetFrom 9.0.09.0.16
20 more packages
dotnet BitnamiFrom 8.0.08.0.27, 9.0.16
dotnet-sdk BitnamiFrom 8.0.08.0.27, 9.0.16
Microsoft.NetCore.App.Runtime.win-arm64 NuGetFrom 10.0.010.0.8
Microsoft.NetCore.App.Runtime.win-arm64 NuGetFrom 10.0.010.0.8
Microsoft.NetCore.App.Runtime.win-arm64 NuGetFrom 8.0.08.0.27
Microsoft.NetCore.App.Runtime.win-arm64 NuGetFrom 8.0.08.0.27
Microsoft.NetCore.App.Runtime.win-arm64 NuGetFrom 9.0.09.0.16
Microsoft.NetCore.App.Runtime.win-arm64 NuGetFrom 9.0.09.0.16
Microsoft.NetCore.App.Runtime.win-x64 NuGetFrom 10.0.010.0.8
Microsoft.NetCore.App.Runtime.win-x64 NuGetFrom 10.0.010.0.8
Microsoft.NetCore.App.Runtime.win-x64 NuGetFrom 8.0.08.0.27
Microsoft.NetCore.App.Runtime.win-x64 NuGetFrom 8.0.08.0.27
Microsoft.NetCore.App.Runtime.win-x64 NuGetFrom 9.0.09.0.16
Microsoft.NetCore.App.Runtime.win-x64 NuGetFrom 9.0.09.0.16
Microsoft.NetCore.App.Runtime.win-x86 NuGetFrom 10.0.010.0.8
Microsoft.NetCore.App.Runtime.win-x86 NuGetFrom 10.0.010.0.8
Microsoft.NetCore.App.Runtime.win-x86 NuGetFrom 8.0.08.0.27
Microsoft.NetCore.App.Runtime.win-x86 NuGetFrom 8.0.08.0.27
Microsoft.NetCore.App.Runtime.win-x86 NuGetFrom 9.0.09.0.16
Microsoft.NetCore.App.Runtime.win-x86 NuGetFrom 9.0.09.0.16

Products include 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.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-32175 being exploited?

There is no known exploitation of CVE-2026-32175 in the wild and no public exploit code.

All Microsoft .Net vulnerabilities

Sources

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 and 1 more.

Is CVE-2026-32175 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free