Patch tracker / CVE reference / CVE-2025-49717

CVE-2025-49717

CVE-2025-49717 is a high severity Microsoft vulnerability with a CVSS score of 8.5. Its EPSS score puts the probability of exploitation in the next 30 days at 11%. Microsoft has shipped the fix: deploy one of the 4 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

8.5

CVSS v3

11%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 11%. CVSS 8.5 (High).

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

Senserva AI Opinion for CVE-2025-49717

Unlike the client-side provider bugs that dominate SQL Server's CVE history, this remote code execution flaw is filed against the SQL Server 2019 and 2022 builds themselves, spanning both GDR and CU 32 servicing lines. Its 10 percent EPSS is five times the level of the OLE DB cluster, and database servers concentrate exactly the data attackers monetize. Severity is High at CVSS 8.5.

Do this: Patch SQL Server 2019 and 2022 instances reachable from application networks before the client-side driver fixes.

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

Senserva AI Opinion and rich prompt for CVE-2025-49717

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

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 KB5058712, KB5058713, KB5058721, KB5058722 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-2025-49717. 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.

KB5058712 KB5058713 KB5058721 KB5058722

Scope and sources

Affected products

Fixed by the same updates

CVE-2025-49718 CVE-2025-49719

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.