Patch tracker / CVE reference / CVE-2026-20876
CVE-2026-20876
CVE-2026-20876 is a medium severity Microsoft vulnerability with a CVSS score of 6.7. Its EPSS score puts the probability of exploitation in the next 30 days at 75%. Microsoft has shipped the fix: deploy one of the 4 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 75%. CVSS 6.7 (Medium).
This CVE is among the top 25% of tracked Microsoft CVEs by EPSS exploit probability.
This bug targets Virtualization-Based Security enclaves, the hardware-backed isolated memory regions meant to protect the most sensitive secrets on a device, on the newest Server 2025 and Windows 11 25H2 builds. A 73 percent EPSS on a bug that undermines VBS enclave protection is particularly concerning since enclaves exist specifically to resist this class of attack.
Do this: Patch Windows 11 25H2 and Server 2025 systems immediately, since this undermines the hardware-backed isolation VBS enclaves are designed to provide.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2026-20876
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Official patch(es) for CVE-2026-20876
High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5073379, KB5073450, KB5073455, KB5074109 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-20876. 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.