Patch tracker / CVE reference / CVE-2024-43474

CVE-2024-43474

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

Risk summary

High

7.6

CVSS v3

2.2%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 2.2%. CVSS 7.6 (High).

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

Senserva AI Opinion for CVE-2024-43474

This is an information disclosure flaw in Microsoft SQL Server, hitting the 2017 GDR and CU 31 servicing branches as well as SQL Server 2019 GDR. A CVSS score of 8.8 is unusually high for a disclosure bug in a database engine, which suggests the data an attacker can read is significant. Exploit probability sits at a modest 2 percent and there is no confirmed exploitation, so this is a patch-cycle item rather than an emergency, but database servers hold the data attackers actually want.

Do this: Inventory your SQL Server 2017 and 2019 instances, confirm which servicing branch (GDR or CU) each is on, and apply the matching security update.

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

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

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

Fixed by KB5042214 and 2 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-43474

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5042214, KB5042215, KB5042217 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-43474. 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.

KB5042214 KB5042215 KB5042217

Scope and sources

Affected products

Fixed by the same updates

CVE-2024-26186 CVE-2024-26191 CVE-2024-37335 CVE-2024-37338 CVE-2024-37339 CVE-2024-37340 CVE-2024-37965 CVE-2024-37980

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.