Patch tracker / CVE reference / CVE-2024-38255

CVE-2024-38255

CVE-2024-38255 is a high severity Microsoft vulnerability with a CVSS score of 8.8. Microsoft has shipped the fix: deploy one of the 6 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.6%

EPSS, 30 days

High

Severity

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

The deprecated SQL Server Native Client driver is the weak point here: a High Severity CVSS 8.8 remote code execution flaw affecting SQL Server 2016 SP3, 2017, and 2019 GDR builds. Exploiting driver bugs in this class generally requires steering a client into connecting to a malicious SQL server, which keeps the EPSS probability at 2 percent. The bigger issue is that this driver is everywhere: it rides along on application servers, not just database hosts.

Do this: Apply the SQL Server GDR update and start cataloging which application servers still have the Native Client installed.

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

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

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

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5046855, KB5046856, KB5046857, KB5046858, KB5046859, KB5046860 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-38255. 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.

KB5046855 KB5046856 KB5046857 KB5046858 KB5046859 KB5046860

Scope and sources

Affected products

Fixed by the same updates

CVE-2024-43459 CVE-2024-43462 CVE-2024-48993 CVE-2024-48994 CVE-2024-48995 CVE-2024-48996 CVE-2024-48997 CVE-2024-48998

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.