Patch tracker / CVE reference / CVE-2026-27931
CVE-2026-27931
CVE-2026-27931 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 one of the 7 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.
Risk summary
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.
GDI renders graphics for countless applications, and this information-disclosure flaw on Windows Server 2022 and Windows 10 21H2 leaks memory through image or drawing operations at CVSS 9.8 and 64 percent EPSS. GDI leaks are attractive because the component is reachable through documents, web content, and print paths. Its mainstream 2022 and 21H2 scope broadens the exposure.
Do this: Apply the cumulative update to Windows Server 2022 and Windows 10 21H2 systems to close the GDI leak.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2026-27931
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Official patch(es) for CVE-2026-27931
High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5082052, KB5082060, KB5082063, KB5082142, KB5082200, KB5083768, KB5083769 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-27931. 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.
Scope and sources
- Affected products
- Fixed by the same updates
- Authoritative references
Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.