CVE-2026-32175

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit probability: 0.7%, top 51% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: cna:microsoft, epss
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 4.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
4.3
EG Score
4.3(medium)
EPSS
49.2%
KEV
Not listed

Published

May 12, 2026

Last Modified

June 19, 2026

Advisory Details (1)

Auto-updated Jun 25, 2026
Patch available. Sources: microsoft.
microsoft Patch Available

Security Update Guide - Microsoft Security Response Center

Security Update Guide - Microsoft Security Response Center. Patch available via Microsoft Security Update

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-32175

Vendor Advisories for CVE-2026-32175(2)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(4 across 1 ecosystem)
NuGet(4)
PackageVulnerable rangeFixed inDependents
Microsoft.NetCore.App.Runtime.win-arm—10.0.8—
Microsoft.NetCore.App.Runtime.win-arm6410.0.0 ... 10.0.7 (8 versions)10.0.8—
Microsoft.NetCore.App.Runtime.win-x6410.0.0 ... 10.0.7 (8 versions)10.0.8—
Microsoft.NetCore.App.Runtime.win-x8610.0.0 ... 10.0.7 (8 versions)10.0.8—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 54× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 125 total refreshes for this CVE.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:15 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-01 15:06 UTCEPSS rescore
  12. 2026-06-30 23:22 UTCEPSS rescore
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-29 14:06 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 14:07 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 04:56 UTCEPSS rescore
  19. 2026-06-28 02:16 UTCEG score recompute
  20. 2026-06-28 02:16 UTCVendor advisory
  21. 2026-06-27 03:08 UTCEPSS rescore
  22. 2026-06-26 23:07 UTCEG score recompute
  23. 2026-06-26 23:07 UTCVendor advisory
  24. 2026-06-25 21:52 UTCEG score recompute
  25. 2026-06-25 21:52 UTCVendor advisory
Show 75 more
  1. 2026-06-25 13:49 UTCEPSS rescore
  2. 2026-06-25 13:49 UTCEPSS rescore
  3. 2026-06-24 14:05 UTCEPSS rescore
  4. 2026-06-23 21:33 UTCEPSS rescore
  5. 2026-06-23 21:33 UTCEPSS rescore
  6. 2026-06-22 14:25 UTCEPSS rescore
  7. 2026-06-22 14:25 UTCEPSS rescore
  8. 2026-06-21 14:56 UTCEPSS rescore
  9. 2026-06-21 14:56 UTCEPSS rescore
  10. 2026-06-21 01:59 UTCEPSS rescore
  11. 2026-06-19 19:25 UTCEPSS rescore
  12. 2026-06-19 19:25 UTCEPSS rescore
  13. 2026-06-18 17:52 UTCEPSS rescore
  14. 2026-06-18 17:52 UTCEPSS rescore
  15. 2026-06-17 17:53 UTCEPSS rescore
  16. 2026-06-16 17:52 UTCEPSS rescore
  17. 2026-06-16 06:32 UTCEG score recompute
  18. 2026-06-16 06:32 UTCVendor advisory
  19. 2026-06-15 17:49 UTCEPSS rescore
  20. 2026-06-15 04:54 UTCEG score recompute
  21. 2026-06-15 04:54 UTCVendor advisory
  22. 2026-06-14 23:18 UTCEPSS rescore
  23. 2026-06-14 03:39 UTCEG score recompute
  24. 2026-06-14 03:39 UTCVendor advisory
  25. 2026-06-13 23:00 UTCEPSS rescore
  26. 2026-06-13 02:19 UTCEG score recompute
  27. 2026-06-13 02:19 UTCVendor advisory
  28. 2026-06-12 23:12 UTCEPSS rescore
  29. 2026-06-12 23:12 UTCEPSS rescore
  30. 2026-06-12 01:04 UTCEG score recompute
  31. 2026-06-12 01:04 UTCVendor advisory
  32. 2026-06-11 14:00 UTCEPSS rescore
  33. 2026-06-10 23:49 UTCEG score recompute
  34. 2026-06-10 23:49 UTCVendor advisory
  35. 2026-06-10 22:18 UTCEPSS rescore
  36. 2026-06-10 13:22 UTCEPSS rescore
  37. 2026-06-09 22:22 UTCEG score recompute
  38. 2026-06-09 22:22 UTCVendor advisory
  39. 2026-06-08 20:12 UTCEG score recompute
  40. 2026-06-08 20:12 UTCVendor advisory
  41. 2026-06-08 14:17 UTCEPSS rescore
  42. 2026-06-08 14:17 UTCEPSS rescore
  43. 2026-06-07 15:25 UTCEPSS rescore
  44. 2026-06-07 15:25 UTCEPSS rescore
  45. 2026-06-07 15:25 UTCEPSS rescore
  46. 2026-06-07 14:10 UTCEG score recompute
  47. 2026-06-07 14:10 UTCVendor advisory
  48. 2026-06-06 13:47 UTCEPSS rescore
  49. 2026-06-06 13:47 UTCEPSS rescore
  50. 2026-06-06 12:51 UTCEG score recompute
  51. 2026-06-06 12:51 UTCVendor advisory
  52. 2026-06-05 22:47 UTCEPSS rescore
  53. 2026-06-05 22:47 UTCEPSS rescore
  54. 2026-06-05 11:36 UTCEG score recompute
  55. 2026-06-05 11:36 UTCVendor advisory
  56. 2026-06-05 06:10 UTCEPSS rescore
  57. 2026-06-05 06:10 UTCEPSS rescore
  58. 2026-06-04 13:12 UTCEPSS rescore
  59. 2026-06-04 13:12 UTCEPSS rescore
  60. 2026-06-04 10:18 UTCEG score recompute
  61. 2026-06-04 10:18 UTCVendor advisory
  62. 2026-06-03 09:03 UTCEG score recompute
  63. 2026-06-03 09:03 UTCVendor advisory
  64. 2026-06-02 20:13 UTCEPSS rescore
  65. 2026-06-02 07:48 UTCEG score recompute
  66. 2026-06-02 07:48 UTCVendor advisory
  67. 2026-06-01 13:51 UTCEPSS rescore
  68. 2026-06-01 13:51 UTCEPSS rescore
  69. 2026-06-01 06:33 UTCEG score recompute
  70. 2026-06-01 06:33 UTCVendor advisory
  71. 2026-05-31 22:30 UTCEPSS rescore
  72. 2026-05-31 22:30 UTCEPSS rescore
  73. 2026-05-31 00:16 UTCEPSS rescore
  74. 2026-05-31 00:16 UTCEPSS rescore
  75. 2026-05-29 13:44 UTCEPSS rescore

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-32175?
CVE-2026-32175 is a medium vulnerability published on May 12, 2026. 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…
When was CVE-2026-32175 disclosed?
CVE-2026-32175 was first published in the National Vulnerability Database on May 12, 2026, with the most recent update on June 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32175 actively exploited?
CVE-2026-32175 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 49.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-32175?
CVE-2026-32175 has a CVSS v4.0 base score of 4.3 (CNA self-assessment; NVD's own analysis pending).
How do I remediate CVE-2026-32175?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32175, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32175

Explore →

Is Your Infrastructure Affected by CVE-2026-32175?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs