Patch tracker / CVE reference / CVE-2026-49173
CVE-2026-49173
CVE-2026-49173 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 64%. Microsoft has shipped the fix: deploy the update 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 64%. CVSS 7.8 (High).
This CVE is among the top half of tracked Microsoft CVEs by EPSS exploit probability.
CVE-2026-49173 is a Windows Kernel elevation of privilege flaw scoped narrowly to Windows 11 version 26H1 on x64 and ARM64 systems, so exposure is limited to organizations already running that specific release. Severity is rated High with a CVSS score of 7.8, meaning a local attacker who already has a foothold could gain kernel-level privileges. It is not listed in CISA KEV and has no known ransomware association at this time.
Do this: Inventory which endpoints are running Windows 11 version 26H1 and apply the kernel patch to those specific x64 and ARM64 machines first.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2026-49173
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Official patch(es) for CVE-2026-49173
High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing update KB5101649 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.
Apply the Microsoft security update below to fix CVE-2026-49173. 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 update
- Authoritative references
Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.