CVE-2026-32175A tampering vulnerability exists when .NET Core improperly handles specially crafted files.
Updated under an hour ago ()
Does this affect you?
It affects microsoft visual_studio_2022 and 2 other products. Add what you run to find out whether that includes you.
No exploitation reported and no EPSS estimate yet.
Do this next
Free account, 1 product
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.
- CVSS
- 4.3 MEDIUM (v3.1, NVD)CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- Weakness (CWE)
- CWE-36, CWE-22
- Known exploited
- Not in CISA's KEV catalog
- EPSS (exploitation in the next 30 days)
- Not loaded for this CVE
- Assigned by
- Not given
- NVD analysis
- Analyzed
- Record last updated
- Jun 18, 2026
- First seen by InfoSec Signals
- Oct 9, 2026
Affected products
microsoft visual_studio_2022 microsoft:visual_studio_2022 | from 17.12.0 before 17.12.20; from 17.14.0 before 17.14.32 | NVD |
microsoft visual_studio_2026 microsoft:visual_studio_2026 | from 18.5.0 before 18.5.3 | NVD |
microsoft .net microsoft:.net | from 8.0.0 before 8.0.27; from 9.0.0 before 9.0.16 | NVD |
References
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-32175vendor-advisory
The CVE record on cve.org NVD's entry
The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.