Patch tracker / CVE reference / CVE-2026-50468
CVE-2026-50468
CVE-2026-50468 is a medium severity Microsoft vulnerability with a CVSS score of 6.5. Microsoft has shipped the fix: deploy one of the 2 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.
Risk summary
Not in the CISA KEV catalog. EPSS exploit probability 1.3%. CVSS 6.5 (Medium).
This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.
CVE-2026-50468 is an information disclosure flaw in Microsoft SQL Server 2025 for x64 systems, affecting both the CU6 and GDR servicing branches, rated Severity Medium with a CVSS score of 6.5. Exposure is limited to organizations already running the 2025 release, which is early enough that many shops may still be piloting it rather than in full production. It is not on the CISA KEV list and has no known ransomware association, so this is a patch on your normal cycle rather than an emergency.
Do this: Identify which of your SQL Server 2025 x64 instances are on the CU6 or GDR branch and apply the matching update for your servicing track.
AI-generated from public data, 2026-07-21. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2026-50468
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Official patch(es) for CVE-2026-50468
Lower priority: patch in your normal cycle. In Intune or Defender, confirm whether the fixing updates KB5101346, KB5102333 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-2026-50468. 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.
Scope and sources
- Affected products
- Fixed by the same updates
- Authoritative references
Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.