Patch tracker / CVE reference / CVE-2024-38160

CVE-2024-38160

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

Risk summary

Critical

9.1

CVSS

71%

EPSS, 30 days

Critical

Severity

Not in the CISA KEV catalog. EPSS exploit probability 71%. CVSS 9.1 (Critical).

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

Senserva AI Opinion for CVE-2024-38160

A companion to CVE-2024-38159, this is the second Critical Severity (CVSS 9.8) Remote Code Execution flaw in Windows Network Virtualization on Server 2016 and Windows 10 1607, also at 71% EPSS. Two simultaneous top-Severity bugs in the same SDN component tell you the attack surface runs deep. Environments running software-defined networking on legacy Hyper-V hosts should treat the pair as one urgent event.

Do this: Confirm the update covering both network virtualization CVEs is applied to every Server 2016 virtualization host in the estate.

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

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

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

High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing update KB5041773 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.

Apply the Microsoft security update below to fix CVE-2024-38160. 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.

KB5041773

Scope and sources

Affected products

Fixed by the same update

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

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.