Patch tracker / CVE reference / CVE-2026-32224

CVE-2026-32224

CVE-2026-32224 is a critical severity Microsoft vulnerability with a CVSS score of 9.8. Its EPSS score puts the probability of exploitation in the next 30 days at 56%. Microsoft has shipped the fix: deploy the update below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

Critical

9.8

CVSS

56%

EPSS, 30 days

Critical

Severity

Not in the CISA KEV catalog. EPSS exploit probability 56%. CVSS 9.8 (Critical).

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

Senserva AI Opinion for CVE-2026-32224

Windows Server Update Service, the very mechanism many organizations rely on to distribute patches, has its own Critical elevation of privilege bug here, which is a particularly uncomfortable irony given the 64 percent EPSS exploit probability. It affects the current Windows 11 26H1 build on both CPU architectures, and a compromised WSUS role could be used to push malicious updates fleet-wide rather than just escalate on one box. No confirmed KEV or ransomware activity yet, but WSUS servers are high-value targets precisely because of that update-distribution trust.

Do this: Patch any server running the WSUS role immediately, since a compromise there can cascade to every client it updates.

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

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

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

Patch this cycle

Not confirmed exploited yet, but the 30-day exploit probability is high (EPSS 56%).

Fixed by KB5083768. Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Patch in this maintenance window; do not let it slip to the next one.

Official patch(es) for CVE-2026-32224

High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing update KB5083768 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.

Apply the Microsoft security update below to fix CVE-2026-32224. 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.

KB5083768

Scope and sources

Affected products

Fixed by the same update

CVE-2025-64720 CVE-2025-65018 CVE-2026-20806 CVE-2026-20928 CVE-2026-23670 CVE-2026-25184 CVE-2026-25250 CVE-2026-26151

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.