Patch tracker / CVE reference / CVE-2026-26116

CVE-2026-26116

CVE-2026-26116 is a high severity Microsoft vulnerability with a CVSS score of 8.8. 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

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-26116

CVE-2026-26116 is an elevation of privilege flaw in Microsoft SQL Server 2025 for x64 systems, hitting both the GDR and CU2 servicing branches. At CVSS 8.8 High, it lets an authenticated database user climb to higher privileges, which matters because SQL Server 2025 is a fresh release and this bug affects its earliest patch levels. There is no confirmed exploitation in the wild and EPSS sits at only 2 percent, so this is a patch-ahead situation rather than a fire drill.

Do this: Identify whether your SQL Server 2025 instances are on the GDR or CU2 branch and apply the matching Microsoft security update for that branch.

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

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

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

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5077466, KB5077468 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-26116. 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.

KB5077466 KB5077468

Scope and sources

Affected products

Fixed by the same updates

CVE-2026-21262 CVE-2026-26115

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.