Patch tracker / CVE reference / CVE-2024-43593
CVE-2024-43593
CVE-2024-43593 is a high severity Microsoft vulnerability with a CVSS score of 8.8. Its EPSS score puts the probability of exploitation in the next 30 days at 67%. Microsoft has shipped the fix: deploy one of the 10 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 67%. CVSS 8.8 (High).
This CVE is among the top 25% of tracked Microsoft CVEs by EPSS exploit probability.
Yet another distinct RRAS bug, this remote code execution vulnerability rates Critical, CVSS 9.0, with a 61 percent EPSS probability on Windows Server 2019 and 2022. Server Core installations are explicitly in scope, so headless remote access boxes cannot be skipped. The mitigating grace is that only servers with the role enabled are exposed.
Do this: Include Server Core machines in your RRAS patch verification, since they are easy to miss in GUI-driven checks.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2024-43593
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Official patch(es) for CVE-2024-43593
High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5044277, KB5044281, KB5044288, KB5044293, KB5044306, KB5044320, KB5044321, KB5044342, KB5044343, KB5044356 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-2024-43593. 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.