Patch tracker / CVE reference / CVE-2026-44813

CVE-2026-44813

CVE-2026-44813 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 54%. 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

High

7.8

CVSS

54%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 54%. CVSS 7.8 (High).

This CVE is among the top half of tracked Microsoft CVEs by EPSS exploit probability.

Senserva AI Opinion for CVE-2026-44813

Fourth of the Windows 11 26H1-only Desktop Window Manager escalations, sharing the Critical (CVSS 9.8) severity and 48 percent EPSS exploit probability of the set. For fleets piloting 26H1, the accumulation matters: a single well-tested exploit against this library family would work across every unpatched 26H1 device, x64 and ARM64 alike. There is no confirmed exploitation or ransomware use yet.

Do this: Gate any further Windows 11 26H1 rollout on devices being fully patched, and audit the existing pilot group today.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-44813

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2026-44813 (source: https://senserva.com/cve/CVE-2026-44813.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-44813: High severity Microsoft vulnerability, CVSS 7.8
- EPSS 30-day exploitation probability: 54%
- Actively exploited (CISA KEV): no
- Fixed by: KB5095051
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Patch this cycle

Not confirmed exploited yet, but the 30-day exploit probability is high (EPSS 54%).

Fixed by KB5095051. Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Patch in this maintenance window; do not let it slip to the next one.

Official patch(es) for CVE-2026-44813

High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing update KB5095051 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-44813. 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.

KB5095051

Scope and sources

Affected products

Fixed by the same update

CVE-2026-42990 CVE-2026-44815 CVE-2026-45642 CVE-2026-45657 CVE-2026-47291 CVE-2026-42904 CVE-2025-10263 CVE-2026-45602

Authoritative references

Official CVE record (cve.org)NVD detail Microsoft MSRC FIRST.org EPSS

Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.