CVE-2026-32175: .NET Core Tampering Vulnerability
Noroxi assessment
Priority: Monitor (action score 17/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.71% (FIRST EPSS); higher than 53.5% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: .NET 10.0 installed on Windows 10.0.8; .NET 8.0 installed on Windows 8.0.27; .NET 9.0 installed on Windows 9.0.16.
Low priority for now. Upgrade to .NET 10.0 installed on Windows 10.0.8; .NET 8.0 installed on Windows 8.0.27; .NET 9.0 installed on Windows 9.0.16 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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
- May 12, 2026
- Updated
- Aug 10, 2026
- EPSS
- 0.7% · 53th percentile
- CWE
- CWE-36
Report tools
Action score
17
Monitor
Low priority for now.
- CVSS
- 17 / 40 · 4.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.7%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 4.3
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | visual studio 2022 | cpe:2.3:a:microsoft:visual_studio_2022 |
| microsoft | visual studio 2026 | cpe:2.3:a:microsoft:visual_studio_2026 |
| microsoft | .net | cpe:2.3:a:microsoft:.net |
| microsoft | windows | cpe:2.3:o:microsoft:windows |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft .net8.0.0 and later · before 8.0.27
- microsoft .net9.0.0 and later · before 9.0.16
- microsoft visual studio 202217.12.0 and later · before 17.12.20
- microsoft visual studio 202217.14.0 and later · before 17.14.32
- microsoft visual studio 202618.5.0 and later · before 18.5.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft .NET 10.0
- 10.0.0 and later · before 10.0.8affected
Microsoft .NET 8.0
- 8.0.0 and later · before 8.0.27affected
Microsoft .NET 9.0
- 9.0.0 and later · before 9.0.16affected
Microsoft Microsoft Visual Studio 2022 version 17.12
- 17.12.0 and later · before 17.12.20affected
Microsoft Microsoft Visual Studio 2022 version 17.14
- 17.14.0 and later · before 17.14.32affected
Microsoft Microsoft Visual Studio 2026 version 18.5
- 18.5.0 and later · before 18.5.3affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| NuGet | Microsoft.NetCore.App.Runtime.win-arm | from 10.0.0 · before 10.0.8 | 10.0.8 |
| NuGet | Microsoft.NetCore.App.Runtime.win-arm | from 8.0.0 · before 8.0.27 | 8.0.27 |
| NuGet | Microsoft.NetCore.App.Runtime.win-arm | from 9.0.0 · before 9.0.16 | 9.0.16 |
| NuGet | Microsoft.NetCore.App.Runtime.win-arm64 | from 10.0.0 · before 10.0.8 | 10.0.8 |
| NuGet | Microsoft.NetCore.App.Runtime.win-arm64 | from 8.0.0 · before 8.0.27 | 8.0.27 |
| NuGet | Microsoft.NetCore.App.Runtime.win-arm64 | from 9.0.0 · before 9.0.16 | 9.0.16 |
| NuGet | Microsoft.NetCore.App.Runtime.win-x64 | from 10.0.0 · before 10.0.8 | 10.0.8 |
| NuGet | Microsoft.NetCore.App.Runtime.win-x64 | from 8.0.0 · before 8.0.27 | 8.0.27 |
| NuGet | Microsoft.NetCore.App.Runtime.win-x64 | from 9.0.0 · before 9.0.16 | 9.0.16 |
| NuGet | Microsoft.NetCore.App.Runtime.win-x86 | from 10.0.0 · before 10.0.8 | 10.0.8 |
| NuGet | Microsoft.NetCore.App.Runtime.win-x86 | from 8.0.0 · before 8.0.27 | 8.0.27 |
| NuGet | Microsoft.NetCore.App.Runtime.win-x86 | from 9.0.0 · before 9.0.16 | 9.0.16 |
Same product
microsoft: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-36758Visual Studio Elevation of Privilege Vulnerability39Monitor
- CVE-2026-71328.NET and Visual Studio Remote Code Execution Vulnerability35Monitor
- CVE-2026-21256GitHub Copilot and Visual Studio Remote Code Execution Vulnerability35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2025-62214Nov 11, 2025 · Visual Studio Remote Code Execution Vulnerability26Monitor
- ← EarlierCVE-2026-21257Feb 10, 2026 · GitHub Copilot and Visual Studio Elevation of Privilege Vulnerability32Monitor
- Later →CVE-2026-32177May 12, 2026 · .NET Elevation of Privilege Vulnerability29Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| .NET 10.0 installed on Windows | 10.0.8 · KB5093446 | Microsoft (MSRC) |
| .NET 8.0 installed on Windows | 8.0.27 · KB5093447 | Microsoft (MSRC) |
| .NET 9.0 installed on Windows | 9.0.16 · KB5093448 | Microsoft (MSRC) |
| Microsoft Visual Studio 2022 version 17.12 | 17.12.20 · Release Notes | Microsoft (MSRC) |
| Microsoft Visual Studio 2022 version 17.14 | 17.14.32 · Release Notes | Microsoft (MSRC) |
| Microsoft Visual Studio 2026 version 18.5 | 18.5.3 · Release Notes | Microsoft (MSRC) |
| NuGet:Microsoft.NetCore.App.Runtime.win-arm | 10.0.8 | Package registry (OSV) |
| NuGet:Microsoft.NetCore.App.Runtime.win-arm | 8.0.27 | Package registry (OSV) |
| NuGet:Microsoft.NetCore.App.Runtime.win-arm | 9.0.16 | Package registry (OSV) |
| NuGet:Microsoft.NetCore.App.Runtime.win-arm64 | 10.0.8 | Package registry (OSV) |
| NuGet:Microsoft.NetCore.App.Runtime.win-arm64 | 8.0.27 | Package registry (OSV) |
| NuGet:Microsoft.NetCore.App.Runtime.win-arm64 | 9.0.16 | Package registry (OSV) |
| NuGet:Microsoft.NetCore.App.Runtime.win-x64 | 10.0.8 | Package registry (OSV) |
| NuGet:Microsoft.NetCore.App.Runtime.win-x64 | 8.0.27 | Package registry (OSV) |
| NuGet:Microsoft.NetCore.App.Runtime.win-x64 | 9.0.16 | Package registry (OSV) |
| NuGet:Microsoft.NetCore.App.Runtime.win-x86 | 10.0.8 | Package registry (OSV) |
| NuGet:Microsoft.NetCore.App.Runtime.win-x86 | 8.0.27 | Package registry (OSV) |
| NuGet:Microsoft.NetCore.App.Runtime.win-x86 | 9.0.16 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- low · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- Low
- Availability impact
- None
Weakness class (CWE)
CWE-36 · Absolute Path TraversalCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.