Patch tracker / CVE reference / CVE-2025-32712
CVE-2025-32712
CVE-2025-32712 is a high severity Microsoft vulnerability with a CVSS score of 8.8. Its EPSS score puts the probability of exploitation in the next 30 days at 82%. Microsoft has shipped the fix: deploy one of the 16 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.
High severity Microsoft vulnerability, CVSS 8.8. Fixed by 16 Microsoft security updates.
Risk summary
Updated July 23, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Senserva AI Opinion for CVE-2025-32712
An 82 percent EPSS score puts this Win32k elevation of privilege flaw in a different league from most of this batch: exploitation is judged highly likely, and Win32k's track record backs that up. Windows 10 1809 and Server 2019 are affected, Severity is High at CVSS 8.8, and it is one of six fixes in this set sharing that same elevated 82 percent probability. These older builds are the exact population where Win32k exploits still work well.
Do this: Patch 1809 and Server 2019 systems immediately; treat the six 82 percent EPSS bugs as your top block after the SharePoint Word flaw.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2025-32712
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2025-32712
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
Exploitation and severity
Not in the CISA KEV catalog. EPSS exploit probability 82%. CVSS 8.8 (High).
This CVE is among the top 5% of tracked Microsoft CVEs by EPSS exploit probability.
Official patch(es) for CVE-2025-32712
High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5060118, KB5060525, KB5060526, KB5060531, KB5060533, KB5060841, KB5060842, KB5060998, KB5060999, KB5061010, KB5061018, KB5061026, KB5061036, KB5061059, KB5061072, KB5061078 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-2025-32712. 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.
Affected products
Common questions about CVE-2025-32712
Is CVE-2025-32712 actively exploited?
It is not currently listed in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score puts the probability of exploitation in the next 30 days at 82%.
What patch fixes CVE-2025-32712?
Microsoft fixed CVE-2025-32712 in KB5060118, KB5060525, KB5060526, KB5060531, KB5060533, KB5060841, KB5060842, KB5060998, KB5060999, KB5061010, KB5061018, KB5061026, KB5061036, KB5061059, KB5061072, KB5061078. Download from the Microsoft Update Catalog, or let Intune, Windows Update, or WSUS deliver it.
Which products are affected by CVE-2025-32712?
Windows 10 Version 1809 for 32-bit Systems, Windows 10 Version 1809 for x64-based Systems, Windows 11 Version 22H2 for ARM64-based Systems, Windows Server 2019, Windows Server 2019 (Server Core installation), Windows Server 2022, Windows Server 2022 (Server Core installation).
Can I ask my own AI about CVE-2025-32712?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2025-32712's key facts: severity, CVSS, EPSS exploit probability, CISA KEV status, and the fixing KB. Copy it into Claude, ChatGPT, or Copilot for a triage plan; the data is refreshed three times a day (5 AM, 12:30 PM, and 7 PM US Central).
Fixed by the same updates
If you are patching CVE-2025-32712, the same updates also fix these:
Authoritative references
Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.
