Patch tracker / CVE reference / CVE-2024-35264

CVE-2024-35264

CVE-2024-35264 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 v3

2.9%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 2.9%. 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-35264

This remote code execution flaw spans the .NET 6.0 and 8.0 runtimes plus Visual Studio 2022 17.4, rated High Severity at CVSS 8.1 with a 3 percent EPSS score. Runtime-level .NET bugs matter beyond developer machines: every production server hosting an ASP.NET application on an unpatched runtime inherits the flaw. Note that .NET 6.0 has since left support, so instances of it need migration, not just patching.

Do this: Update .NET 8.0 runtimes on application servers, patch Visual Studio on developer machines, and schedule migration for anything still on .NET 6.0.

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

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

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

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

KB5041081

Scope and sources

Affected products

Fixed by the same update

CVE-2024-30105 CVE-2024-38095

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.