Loading vulnerability…
CVE-2026-32175 is a tampering vulnerability in .NET Core/.NET caused by improper handling of specially crafted files. When a vulnerable runtime processes attacker-supplied crafted file content, it can be induced to create or write arbitrary files and directories in certain locations on the target system. The attacker’s control over the final destination is limited, but the flaw still enables unauthorized modification of filesystem state. Affected product lines include .NET 8.0, .NET 9.0, and .NET 10.0.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A .NET security fix mentioned only as another CVE included in the same monthly servicing cycle.
A tampering vulnerability affecting supported .NET versions, fixed in the May 2026 servicing updates.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.