Microsoft · .NET · published 2026-05-12

CVE-2026-32175.NET Core Tampering Vulnerability

Routine No exploitation evidence; EPSS 0.7%.

CVE-2026-32175 is not known to be exploited in the wild. EPSS estimates a 0.7% chance of exploitation in the next 30 days, higher than 54% of all CVEs. This .NET vulnerability: CVSS 4.3 (v3.1). Fixed upstream in .NET 10.0.8. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in .NET 10.0.8.

Patch events

  1. This monthSecurity release

    Language runtime.NET

    .NET security release: 10.0.8

    Upgrade to 10.0.8

    Why: CVE-2026-42899: EPSS 2.4% with high severity (CVSS 7.5).

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.7% (54th pct)FIRST EPSS v2026.06.15
CVSS base score4.3 (v3.1)
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
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableNoCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

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.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →