Patch tracker / CVE reference / CVE-2026-32177

CVE-2026-32177

CVE-2026-32177 is a high severity Microsoft vulnerability with a CVSS score of 7.3. Microsoft has shipped the fix: deploy one of the 20 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

7.3

CVSS v3

2.4%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 2.4%. CVSS 7.3 (High).

This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.

Senserva AI Opinion for CVE-2026-32177

CVE-2026-32177 is an elevation of privilege flaw spanning three supported .NET runtime branches (8.0, 9.0, and 10.0) on Windows, so any Windows host running .NET apps or the .NET runtime is potentially in scope rather than a single niche product. Severity is High with a CVSS score of 7.5, but EPSS exploit probability sits at 2 percent, it is not in CISA KEV, and there is no known ransomware use, so this is a patch-on-schedule item rather than a fire drill.

Do this: Inventory Windows machines running .NET 8.0, 9.0, or 10.0 and apply the corresponding Microsoft runtime updates for all installed branches in your next patch cycle.

AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-32177

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2026-32177 (source: https://senserva.com/cve/CVE-2026-32177.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-32177: High severity Microsoft vulnerability, CVSS 7.3
- EPSS 30-day exploitation probability: 2.4%
- Actively exploited (CISA KEV): no
- Fixed by: KB5087048, KB5087049, KB5087051, KB5087053, KB5087054, KB5087055, KB5087058, KB5087059, KB5087061, KB5087062, KB5087063, KB5087064, KB5087065, KB5087066, KB5087067, KB5087068, KB5087069, KB5093446, KB5093447, KB5093448
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Schedule normally

No exploitation observed: not in the CISA KEV catalog, EPSS 2%.

Fixed by KB5087048 and 19 more (by build, listed below). Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Official patch(es) for CVE-2026-32177

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5087048, KB5087049, KB5087051, KB5087053, KB5087054, KB5087055, KB5087058, KB5087059, KB5087061, KB5087062, KB5087063, KB5087064, KB5087065, KB5087066, KB5087067, KB5087068, KB5087069, KB5093446, KB5093447, KB5093448 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.

Apply the Microsoft security updates below to fix CVE-2026-32177. Each KB page carries the Microsoft Update Catalog download, Microsoft's known issues for the update, a copy-paste PowerShell check for whether it is installed, and the Senserva AI read.

KB5087048 KB5087049 KB5087051 KB5087053 KB5087054 KB5087055 KB5087058 KB5087059 KB5087061 KB5087062 KB5087063 KB5087064 KB5087065 KB5087066 KB5087067 KB5087068 KB5087069 KB5093446 KB5093447 KB5093448

Scope and sources

Affected products

Fixed by the same updates

CVE-2026-32175 CVE-2026-42899 CVE-2026-35433

Authoritative references

Official CVE record (cve.org)NVD detail Microsoft MSRC FIRST.org EPSS

Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.