Patch tracker / CVE reference / CVE-2026-26115

CVE-2026-26115

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

2.0%

EPSS, 30 days

High

Severity

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

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

Senserva AI Opinion for CVE-2026-26115

This is an elevation of privilege flaw spanning a wide range of SQL Server versions, from the newer SQL Server 2025 back to SQL Server 2016 Service Pack 3, all delivered through the GDR servicing branch. At CVSS 8.8 it is rated High Severity, and the combination of privilege gain plus database engines that often hold sensitive data makes it worth prioritizing even though EPSS sits at just 2 percent and it is not in CISA KEV or tied to ransomware. The breadth of affected releases means many shops running older instances alongside 2025 are exposed on multiple fronts.

Do this: Identify every SQL Server 2016 SP3, 2017, and 2025 x64 instance and apply the GDR security update to each, starting with any engine reachable by lower privileged accounts.

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

Senserva AI Opinion and rich prompt for CVE-2026-26115

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-2026-26115 (source: https://senserva.com/cve/CVE-2026-26115.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-26115: High severity Microsoft vulnerability, CVSS 8.8
- EPSS 30-day exploitation probability: 2.0%
- Actively exploited (CISA KEV): no
- Fixed by: KB5077464, KB5077465, KB5077466, KB5077468, KB5077469, KB5077470, KB5077471, KB5077472, KB5077473, KB5077474
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 KB5077464 and 9 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-2026-26115

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5077464, KB5077465, KB5077466, KB5077468, KB5077469, KB5077470, KB5077471, KB5077472, KB5077473, KB5077474 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-26115. 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.

KB5077464 KB5077465 KB5077466 KB5077468 KB5077469 KB5077470 KB5077471 KB5077472 KB5077473 KB5077474

Scope and sources

Affected products

Fixed by the same updates

CVE-2026-21262 CVE-2026-26116

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.