Patch tracker / CVE reference / CVE-2024-38229

CVE-2024-38229

CVE-2024-38229 is a high severity Microsoft vulnerability with a CVSS score of 8.1. 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

High

8.1

CVSS

3.0%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 3.0%. CVSS 8.1 (High).

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

Senserva AI Opinion for CVE-2024-38229

This is a Remote Code Execution flaw in the .NET runtime as surfaced through Visual Studio 2022 versions 17.6, 17.8, and 17.10, with a CVSS score of 8.1 and Severity rated High. Anyone running these Visual Studio 2022 builds on developer machines or build agents is exposed. It is not in CISA KEV, has no known ransomware use, and the EPSS exploit probability sits at 3 percent, so this is patch-on-schedule rather than drop-everything.

Do this: Push the latest Visual Studio 2022 updates for the 17.6, 17.8, and 17.10 channels to all developer workstations and build servers this maintenance cycle.

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

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

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-38229 (source: https://senserva.com/cve/CVE-2024-38229.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2024-38229: High severity Microsoft vulnerability, CVSS 8.1
- EPSS 30-day exploitation probability: 3.0%
- Actively exploited (CISA KEV): no
- Fixed by: KB5045993
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: not in the CISA KEV catalog, EPSS 3%.

Fixed by KB5045993. 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-38229

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing update KB5045993 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-38229. 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.

KB5045993

Scope and sources

Affected products

Fixed by the same update

CVE-2024-43483 CVE-2024-43484 CVE-2024-43485

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.