Patch tracker / CVE reference / CVE-2025-59499

CVE-2025-59499

CVE-2025-59499 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.1%

EPSS, 30 days

High

Severity

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

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

Senserva AI Opinion for CVE-2025-59499

CVE-2025-59499 is a High severity (CVSS 8.8) elevation of privilege flaw in Microsoft SQL Server 2016 SP3, 2017, and 2019 (all x64 GDR builds). The 8.8 score points to an authenticated attacker escalating from a low-privilege database account to broader control on the SQL host, so any user with even limited query access is a potential path. It is not in CISA KEV and EPSS sits at 1 percent, so there is no confirmed exploitation yet, but SQL Server instances often hold sensitive data that makes escalation attractive.

Do this: Apply the GDR security update for your specific SQL Server 2016 SP3, 2017, or 2019 build and review who currently holds low-privilege login access to those instances.

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

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

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-59499 (source: https://senserva.com/cve/CVE-2025-59499.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2025-59499: High severity Microsoft vulnerability, CVSS 8.8
- EPSS 30-day exploitation probability: 1.1%
- Actively exploited (CISA KEV): no
- Fixed by: KB5068400, KB5068401, KB5068402, KB5068403, KB5068404, KB5068405, KB5068406, KB5068407
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 KB5068400 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-2025-59499

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5068400, KB5068401, KB5068402, KB5068403, KB5068404, KB5068405, KB5068406, KB5068407 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-59499. 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.

KB5068400 KB5068401 KB5068402 KB5068403 KB5068404 KB5068405 KB5068406 KB5068407

Scope and sources

Affected products

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.