Patch tracker / CVE reference / CVE-2024-37341

CVE-2024-37341

CVE-2024-37341 is a high severity Microsoft vulnerability with a CVSS score of 8.8. Microsoft has shipped the fix: deploy one of the 8 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

8.8

CVSS v3

1.5%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 1.5%. CVSS 8.8 (High).

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

Senserva AI Opinion for CVE-2024-37341

At a 1 percent EPSS probability, this SQL Server elevation of privilege flaw is among the least likely in this set to be exploited, though it remains High Severity at CVSS 8.8 for SQL Server 2016 SP3, 2017, and 2019. Its value to an attacker is post-compromise: converting limited database access into broader control. Defense in depth argues for patching it with the rest of the SQL batch.

Do this: Roll this fix into your consolidated SQL Server update rather than tracking it separately.

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

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

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-37341 (source: https://senserva.com/cve/CVE-2024-37341.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2024-37341: High severity Microsoft vulnerability, CVSS 8.8
- EPSS 30-day exploitation probability: 1.5%
- Actively exploited (CISA KEV): no
- Fixed by: KB5046056, KB5046057, KB5046058, KB5046059, KB5046060, KB5046061, KB5046062, KB5046063
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 1%.

Fixed by KB5046056 and 7 more (by build, listed below). 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-37341

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5046056, KB5046057, KB5046058, KB5046059, KB5046060, KB5046061, KB5046062, KB5046063 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-37341. 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.

KB5046056 KB5046057 KB5046058 KB5046059 KB5046060 KB5046061 KB5046062 KB5046063

Scope and sources

Affected products

Fixed by the same updates

CVE-2024-49000

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.