CVE-2026-32177

HIGHPre-NVD 7.37.3—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 57% 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: epss, secondary
7.3EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.3Exploit: None knownExposed: 0

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

Heap-based buffer overflow in .NET allows an unauthorized attacker to elevate privileges locally.

CVSS v3
7.3
EG Score
7.3(medium)
EG Risk
33(Track)
EG Risk 33/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
Severity73% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
43%
KEV
Not listed

Published

May 12, 2026

Last Modified

July 15, 2026

Advisory Details (1)

Auto-updated Jun 11, 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-32177

Vendor Advisories for CVE-2026-32177(1)

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

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 45× 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 150 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-32177?
CVE-2026-32177 is a high vulnerability published on May 12, 2026. Heap-based buffer overflow in .NET allows an unauthorized attacker to elevate privileges locally.
When was CVE-2026-32177 disclosed?
CVE-2026-32177 was first published in the National Vulnerability Database on May 12, 2026, with the most recent update on July 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32177 actively exploited?
CVE-2026-32177 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 57.1% of all scored CVEs.
What is the CVSS score of CVE-2026-32177?
CVE-2026-32177 has a CVSS v3 base score of 7.3 (NVD).
How do I remediate CVE-2026-32177?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32177, 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

Explore the affected products and dependency analysis for CVE-2026-32177

Explore →

Is Your Infrastructure Affected by CVE-2026-32177?

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

Start Free Scan →Browse All CVEs