Patch tracker / CVE reference / CVE-2024-49000

CVE-2024-49000

CVE-2024-49000 is a high severity Microsoft vulnerability with a CVSS score of 8.8. Its EPSS score puts the probability of exploitation in the next 30 days at 11%. 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

11%

EPSS, 30 days

High

Severity

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

This Native Client flaw breaks from its siblings on one metric: EPSS rates its exploit probability at 10 percent, five times the rest of the batch. It remains a High Severity CVSS 8.8 remote code execution issue affecting SQL Server 2016 SP3, 2017, and 2019. The elevated score is a reason to lead your Native Client remediation with this specific CVE.

Do this: Patch this CVE ahead of the other Native Client bugs, starting with clients that connect across trust boundaries.

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

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

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

Patch this cycle

Not confirmed exploited yet, but the 30-day exploit probability is high (EPSS 11%).

Fixed by KB5046062 and 5 more (by build, listed below). Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Patch in this maintenance window; do not let it slip to the next one.

Official patch(es) for CVE-2024-49000

Elevated priority: high severity or a meaningful exploitation probability, sooner if an affected product is internet-facing. In Intune or Defender, confirm whether the fixing updates KB5046062, KB5046857, KB5046858, KB5046859, KB5046860, KB5058718 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-49000. 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.

KB5046062 KB5046857 KB5046858 KB5046859 KB5046860 KB5058718

Scope and sources

Affected products

Fixed by the same updates

CVE-2024-37341 CVE-2024-38255 CVE-2024-43459 CVE-2024-43462 CVE-2024-48993 CVE-2024-48994 CVE-2024-48995 CVE-2024-48996

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.