CVE-2026-32175 | .NET Core Tampering Vulnerability

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.

Published: 2026-05-12 Last update: 2026-05-13 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-32175 is rated Low Risk (20.9/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.04%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-32175

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-05-22 0.08% 0.04% -0.04%
2 2026-05-13 0.08%

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-32175

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
4.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 1.4 [email protected]

Weakness enumeration for CVE-2026-32175

GitHub Security Advisory for CVE-2026-32175

GHSA-rg75-q538-x34v · Severity: high · Ecosystem: nuget — Microsoft Security Advisory CVE-2026-32175 – .NET Core Tampering Vulnerability

OS Trackers for CVE-2026-32175

vendor priority summary link
ubuntu medium CVE-2026-32175 medium priority: Ubuntu including 5 source packages (dotnet10, dotnet6, dotnet7, dotnet8, dotnet9), 45 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): DNE 31, not-affected 8, needs-triage 5, ignored 1. https://ubuntu.com/security/CVE-2026-32175

Affected software / configurations for CVE-2026-32175

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2026-32175

cvelogic Threat Intelligence