Patch tracker / CVE reference / CVE-2024-38161

CVE-2024-38161

CVE-2024-38161 is a Microsoft vulnerability with a CVSS score of 7.8 (High). Microsoft has shipped the fix: deploy one of the 3 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.

Risk summary

High

7.8

CVSS v3

1.2%

EPSS, 30 days

High

Severity

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

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

Senserva AI Opinion for CVE-2024-38161

A final, lower-severity Mobile Broadband Driver RCE bug appears with a High 7.8 rating and just 1 percent EPSS, a sharp contrast to the 61 percent seen in the other RCE variants for the same driver. This one can be scheduled with routine maintenance rather than treated as urgent.

Do this: Include this with the routine patch cycle; the low EPSS does not justify accelerating ahead of the higher-likelihood driver fixes.

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

Senserva AI Opinion and rich prompt for CVE-2024-38161

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-38161 (source: https://senserva.com/cve/CVE-2024-38161.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed daily (early morning US Central)):
- CVE-2024-38161: Microsoft vulnerability, CVSS 7.8 (High)
- EPSS 30-day exploitation probability: 1.2%
- Actively exploited (CISA KEV): no
- Fixed by: KB5040427, KB5040430, KB5040431
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.

Schedule normally

No exploitation observed as of 2026-10-20: not in the CISA KEV catalog, EPSS 1%.

Fixed by KB5040427 and 2 more (by build, listed below). Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Official patch(es) for CVE-2024-38161

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5040427, KB5040430, KB5040431 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-38161. 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.

KB5040427 KB5040430 KB5040431

Scope and sources

Affected products

Fixed by the same updates

CVE-2024-38184 CVE-2024-38185 CVE-2024-38186 CVE-2024-38187 CVE-2024-38191

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.