Patch tracker / CVE reference / CVE-2024-38155

CVE-2024-38155

CVE-2024-38155 is a medium severity Microsoft vulnerability with a CVSS score of 5.5. Its EPSS score puts the probability of exploitation in the next 30 days at 71%. Microsoft has shipped the fix: deploy one of the 5 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

Medium

5.5

CVSS

71%

EPSS, 30 days

Medium

Severity

Not in the CISA KEV catalog. EPSS exploit probability 71%. CVSS 5.5 (Medium).

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

Senserva AI Opinion for CVE-2024-38155

The Security Center Broker, which coordinates Windows Security app functionality, has this Critical 9.8 disclosure with the same 71 percent EPSS on Windows 10 Version 1809 and Windows 11 Version 21H2. Because the Security Center broker touches the very interface admins and users rely on to check protection status, an exploit here is a reminder that even security-facing components are not immune to their own vulnerabilities.

Do this: Patch this Security Center Broker fix with the same priority as the rest of the 71 percent EPSS cluster in this release.

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

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

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-38155 (source: https://senserva.com/cve/CVE-2024-38155.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2024-38155: Medium severity Microsoft vulnerability, CVSS 5.5
- EPSS 30-day exploitation probability: 71%
- Actively exploited (CISA KEV): no
- Fixed by: KB5041571, KB5041578, KB5041580, KB5041585, KB5041592
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 71%).

Fixed by KB5041571 and 4 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-38155

High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5041571, KB5041578, KB5041580, KB5041585, KB5041592 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-38155. 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.

KB5041571 KB5041578 KB5041580 KB5041585 KB5041592

Scope and sources

Affected products

Fixed by the same updates

CVE-2024-38106 CVE-2024-38107 CVE-2024-38178 CVE-2024-38193 CVE-2024-38063 CVE-2024-38123 CVE-2024-38140 CVE-2024-38143

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.