Patch tracker / CVE reference / CVE-2025-59203
CVE-2025-59203
CVE-2025-59203 is a medium severity Microsoft vulnerability with a CVSS score of 5.5. Microsoft has shipped the fix: deploy one of the 8 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 6.0%. CVSS 5.5 (Medium).
This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.
The State Repository, which backs the app package and settings database on modern Windows, has this Critical 9.9 file information disclosure on Windows 11 Version 25H2 and Windows 10 Version 1809. Because the State Repository holds metadata for installed apps, an exploit could expose installed-application details beyond what an unprivileged process should see. EPSS remains at the modest 6 percent seen across most of this release's fixes.
Do this: Apply this update as part of the standard 25H2 and 1809 patch cycle; no distinct workaround is available outside the official fix.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2025-59203
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Official patch(es) for CVE-2025-59203
Lower priority: patch in your normal cycle. In Intune or Defender, confirm whether the fixing updates KB5066586, KB5066780, KB5066782, KB5066791, KB5066793, KB5066835, KB5066836, KB5066837 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-59203. 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.