Patch tracker / CVE reference / CVE-2024-38134

CVE-2024-38134

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

Risk summary

High

7.8

CVSS

71%

EPSS, 30 days

High

Severity

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

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

Senserva AI Opinion for CVE-2024-38134

This kernel streaming WOW thunk escalation reaches beyond the old branch to include Windows 11 Version 24H2 alongside Windows 10 Version 1809, at Critical Severity (CVSS 9.8) with 71 percent EPSS. The affected translation layer sits in the same code family that dominated escalation findings this cycle. Both new and old builds carry the same underlying code.

Do this: Do not scope this patch to legacy systems; include current Windows 11 24H2 devices in the same deployment.

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

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

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-38134 (source: https://senserva.com/cve/CVE-2024-38134.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2024-38134: High severity Microsoft vulnerability, CVSS 7.8
- EPSS 30-day exploitation probability: 71%
- Actively exploited (CISA KEV): no
- Fixed by: KB5041160, KB5041571, KB5041573, KB5041578, KB5041580, KB5041585, KB5041592, KB5041773, KB5041782, KB5041823, KB5041828, KB5041838, KB5041847, KB5041850
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 KB5041160 and 13 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-38134

High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5041160, KB5041571, KB5041573, KB5041578, KB5041580, KB5041585, KB5041592, KB5041773, KB5041782, KB5041823, KB5041828, KB5041838, KB5041847, KB5041850 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-38134. 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.

KB5041160 KB5041571 KB5041573 KB5041578 KB5041580 KB5041585 KB5041592 KB5041773 KB5041782 KB5041823 KB5041828 KB5041838 KB5041847 KB5041850

Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.

CVE-2024-38134

Risk summary

Official patch(es) for CVE-2024-38134

Scope and sources