Patch tracker / CVE reference / CVE-2024-43540
CVE-2024-43540
CVE-2024-43540 is a medium severity Microsoft vulnerability with a CVSS score of 6.5. Its EPSS score puts the probability of exploitation in the next 30 days at 67%. Microsoft has shipped the fix: deploy one of the 6 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 6.5 (Medium).
This CVE is among the top 25% of tracked Microsoft CVEs by EPSS exploit probability.
A third mobile broadband driver denial of service issue, again Critical 9.0 and 61 percent EPSS, affects the same Windows 10 1809 and Server 2019 builds as its two companions. At this point the pattern matters more than the individual CVE: Microsoft clearly found repeated weaknesses in how this driver parses input. It is not confirmed exploited or ransomware-linked.
Do this: Confirm the cumulative update installed on affected hosts covers all mobile broadband driver CVEs in this release, not just one.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2024-43540
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Official patch(es) for CVE-2024-43540
High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5044273, KB5044277, KB5044280, KB5044284, KB5044285, KB5044288 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-43540. 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.