Patch tracker / CVE reference / CVE-2024-43557

CVE-2024-43557

CVE-2024-43557 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

Medium

6.5

CVSS

67%

EPSS, 30 days

Medium

Severity

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.

Senserva AI Opinion for CVE-2024-43557

Another instance of the recurring Windows Mobile Broadband Driver denial of service issue, again Critical 9.0 and 61 percent EPSS, targets the same Windows 10 1809 and Server 2019 builds. The sheer number of near-duplicate CVEs against this one driver suggests it was a focused area of Microsoft's internal fuzzing or code audit that cycle. There is no confirmed exploitation or ransomware tie.

Do this: Treat the mobile broadband driver as a single patch target and verify the update addresses every related CVE, not just this 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-43557

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-2024-43557 (source: https://senserva.com/cve/CVE-2024-43557.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2024-43557: Medium severity Microsoft vulnerability, CVSS 6.5
- EPSS 30-day exploitation probability: 67%
- Actively exploited (CISA KEV): no
- Fixed by: KB5044273, KB5044277, KB5044280, KB5044284, KB5044285, KB5044288
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 67%).

Fixed by KB5044273 and 5 more (by build, listed below). 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-2024-43557

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-43557. 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.

KB5044273 KB5044277 KB5044280 KB5044284 KB5044285 KB5044288

Scope and sources

Affected products

Fixed by the same updates

CVE-2024-43572 CVE-2024-43573 CVE-2024-38124 CVE-2024-38212 CVE-2024-38265 CVE-2024-43453 CVE-2024-43517 CVE-2024-43518

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.