Patch tracker / CVE reference / CVE-2026-32178

CVE-2026-32178

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

Risk summary

High

7.5

CVSS v3

2.3%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 2.3%. CVSS 7.5 (High).

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

Senserva AI Opinion for CVE-2026-32178

A spoofing flaw in .NET affecting Visual Studio 2022 versions 17.12 and 17.14 plus the .NET 10.0 runtime on Windows, rated High Severity at CVSS 7.5. Spoofing in a framework layer typically means applications can be fed content that misrepresents its origin, undermining trust decisions the app makes. With a 2 percent exploit probability this is routine-cycle work, mostly landing on developer machines and .NET 10 application hosts.

Do this: Update Visual Studio 2022 to a patched 17.12 or 17.14 servicing release and refresh .NET 10 runtimes alongside it.

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

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

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-32178 (source: https://senserva.com/cve/CVE-2026-32178.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-32178: High severity Microsoft vulnerability, CVSS 7.5
- EPSS 30-day exploitation probability: 2.3%
- Actively exploited (CISA KEV): no
- Fixed by: KB5086095, KB5086096, KB5086097
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 KB5086095 and 2 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-32178

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5086095, KB5086096, KB5086097 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-32178. 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.

KB5086095 KB5086096 KB5086097

Scope and sources

Affected products

Fixed by the same updates

CVE-2026-26171 CVE-2026-32203 CVE-2026-33116

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.