Patch tracker / CVE reference / CVE-2024-38246

CVE-2024-38246

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

Risk summary

High

7.0

CVSS

52%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 52%. CVSS 7.0 (High).

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

Senserva AI Opinion for CVE-2024-38246

Win32k again appears with an elevation of privilege bug, this time on Server 2022 and the older Windows 11 21H2, rated Critical with a 71 percent EPSS. Given Win32k's history as one of the most commonly weaponized privilege escalation surfaces, a 71 percent exploitation likelihood should be read as a strong signal to prioritize.

Do this: Patch Server 2022 and Windows 11 21H2 systems for this Win32k fix ahead of lower-EPSS items in the same 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-38246

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-38246 (source: https://senserva.com/cve/CVE-2024-38246.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2024-38246: High severity Microsoft vulnerability, CVSS 7.0
- EPSS 30-day exploitation probability: 52%
- Actively exploited (CISA KEV): no
- Fixed by: KB5042880, KB5042881, KB5043055, KB5043064, KB5043067, KB5043076, KB5043080
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 52%).

Fixed by KB5042880 and 6 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-38246

High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5042880, KB5042881, KB5043055, KB5043064, KB5043067, KB5043076, KB5043080 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-38246. 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.

KB5042880 KB5042881 KB5043055 KB5043064 KB5043067 KB5043076 KB5043080

Scope and sources

Affected products

Fixed by the same updates

CVE-2024-43461 CVE-2024-38014 CVE-2024-38217 CVE-2024-38259 CVE-2024-38260 CVE-2024-43455 CVE-2024-21416 CVE-2024-38045

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.