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 49% 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
Trending — 3 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 4.3Exploit: None knownExposed: 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)
EG Risk
20(Track)
EG Risk 20/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity43% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
51%
KEV
Not listed

Published

May 12, 2026

Last Modified

August 10, 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 190 total refreshes for this CVE.

  1. 2026-08-25 13:49 UTCEPSS rescore
  2. 2026-08-24 14:17 UTCEPSS rescore
  3. 2026-08-23 18:20 UTCEG score recompute
  4. 2026-08-23 18:20 UTCVendor advisory
  5. 2026-08-23 00:19 UTCEPSS rescore
  6. 2026-08-21 23:49 UTCEPSS rescore
  7. 2026-08-20 22:55 UTCEPSS rescore
  8. 2026-08-20 22:55 UTCEPSS rescore
  9. 2026-08-19 17:03 UTCEPSS rescore
  10. 2026-08-18 13:48 UTCEPSS rescore
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-17 10:53 UTCEG score recompute
  13. 2026-08-17 10:53 UTCVendor advisory
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 04:15 UTCEG score recompute
  16. 2026-08-16 04:15 UTCVendor advisory
  17. 2026-08-16 02:14 UTCEPSS rescore
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 02:45 UTCEG score recompute
  20. 2026-08-14 02:45 UTCVendor advisory
  21. 2026-08-13 22:00 UTCEPSS rescore
  22. 2026-08-12 18:02 UTCEG score recompute
  23. 2026-08-12 18:02 UTCVendor advisory
  24. 2026-08-12 13:50 UTCEPSS rescore
  25. 2026-08-11 16:47 UTCEG score recompute
Show 75 more
  1. 2026-08-11 16:47 UTCVendor advisory
  2. 2026-08-11 00:00 UTCEPSS rescore
  3. 2026-08-10 05:14 UTCEG score recompute
  4. 2026-08-10 05:14 UTCVendor advisory
  5. 2026-08-09 13:46 UTCEPSS rescore
  6. 2026-08-09 03:59 UTCEG score recompute
  7. 2026-08-09 03:59 UTCVendor advisory
  8. 2026-08-08 16:37 UTCEPSS rescore
  9. 2026-08-08 02:45 UTCEG score recompute
  10. 2026-08-08 02:45 UTCVendor advisory
  11. 2026-08-07 01:30 UTCEG score recompute
  12. 2026-08-07 01:30 UTCVendor advisory
  13. 2026-08-06 13:46 UTCEPSS rescore
  14. 2026-08-05 21:49 UTCEG score recompute
  15. 2026-08-05 21:49 UTCVendor advisory
  16. 2026-08-05 19:17 UTCEPSS rescore
  17. 2026-08-04 15:10 UTCEPSS rescore
  18. 2026-08-04 10:38 UTCEPSS rescore
  19. 2026-08-04 01:51 UTCEG score recompute
  20. 2026-08-03 10:36 UTCEPSS rescore
  21. 2026-08-03 00:36 UTCEG score recompute
  22. 2026-08-03 00:36 UTCVendor advisory
  23. 2026-08-02 02:27 UTCEPSS rescore
  24. 2026-08-01 23:19 UTCEG score recompute
  25. 2026-08-01 23:19 UTCVendor advisory
  26. 2026-08-01 04:16 UTCEPSS rescore
  27. 2026-07-30 16:28 UTCEPSS rescore
  28. 2026-07-30 01:30 UTCEPSS rescore
  29. 2026-07-28 15:36 UTCEPSS rescore
  30. 2026-07-26 14:54 UTCEPSS rescore
  31. 2026-07-26 14:54 UTCEPSS rescore
  32. 2026-07-25 14:18 UTCEPSS rescore
  33. 2026-07-25 14:17 UTCEPSS rescore
  34. 2026-07-24 14:17 UTCEPSS rescore
  35. 2026-07-23 14:18 UTCEPSS rescore
  36. 2026-07-23 14:18 UTCEPSS rescore
  37. 2026-07-23 03:08 UTCEG score recompute
  38. 2026-07-22 14:08 UTCEPSS rescore
  39. 2026-07-22 14:08 UTCEPSS rescore
  40. 2026-07-21 15:24 UTCEPSS rescore
  41. 2026-07-21 15:24 UTCEPSS rescore
  42. 2026-07-20 17:08 UTCEPSS rescore
  43. 2026-07-20 17:08 UTCEPSS rescore
  44. 2026-07-19 14:31 UTCEPSS rescore
  45. 2026-07-19 14:31 UTCEPSS rescore
  46. 2026-07-19 02:29 UTCEPSS rescore
  47. 2026-07-18 10:04 UTCEPSS rescore
  48. 2026-07-18 10:04 UTCEPSS rescore
  49. 2026-07-16 17:03 UTCEPSS rescore
  50. 2026-07-16 17:03 UTCEPSS rescore
  51. 2026-07-16 02:19 UTCOSV refresh
  52. 2026-07-15 16:57 UTCEPSS rescore
  53. 2026-07-15 16:57 UTCEPSS rescore
  54. 2026-07-15 02:00 UTCEPSS rescore
  55. 2026-07-15 02:00 UTCEPSS rescore
  56. 2026-07-13 22:30 UTCEPSS rescore
  57. 2026-07-13 06:13 UTCEPSS rescore
  58. 2026-07-13 06:13 UTCEPSS rescore
  59. 2026-07-12 05:46 UTCEPSS rescore
  60. 2026-07-11 08:27 UTCEPSS rescore
  61. 2026-07-09 19:10 UTCEPSS rescore
  62. 2026-07-08 15:15 UTCEPSS rescore
  63. 2026-07-07 13:46 UTCEPSS rescore
  64. 2026-07-06 16:27 UTCEPSS rescore
  65. 2026-07-06 16:27 UTCEPSS rescore
  66. 2026-07-06 02:23 UTCEPSS rescore
  67. 2026-07-06 02:23 UTCEPSS rescore
  68. 2026-07-05 02:30 UTCEPSS rescore
  69. 2026-07-04 06:31 UTCEPSS rescore
  70. 2026-07-01 15:06 UTCEPSS rescore
  71. 2026-06-30 23:22 UTCEPSS rescore
  72. 2026-06-29 14:06 UTCEPSS rescore
  73. 2026-06-29 14:06 UTCEPSS rescore
  74. 2026-06-28 14:07 UTCEPSS rescore
  75. 2026-06-28 14:07 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 August 10, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 49.2% of all scored CVEs.
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