Patch tracker / CVE reference / CVE-2025-21325
CVE-2025-21325
CVE-2025-21325 is a high severity Microsoft vulnerability with a CVSS score of 7.8. Its EPSS score puts the probability of exploitation in the next 30 days at 81%. 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
Not in the CISA KEV catalog. EPSS exploit probability 81%. CVSS 7.8 (High).
This CVE is among the top 10% of tracked Microsoft CVEs by EPSS exploit probability.
A flaw in Windows Secure Kernel Mode undermines the virtualization-based security layer that features like Credential Guard depend on, here affecting Windows 10 Version 21H2 across 32-bit, x64, and ARM64. It is rated Critical at CVSS 9.8 with an 81 percent EPSS score, meaning exploitation is judged highly likely. Escalation into the secure kernel erodes exactly the protections designed to survive a compromise.
Do this: Update Windows 10 21H2 devices promptly, starting with machines that rely on Credential Guard or other VBS protections.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2025-21325
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Official patch(es) for CVE-2025-21325
High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5049981, KB5050009, KB5050021 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-21325. 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.