Patch tracker / CVE reference / CVE-2026-32167

CVE-2026-32167

CVE-2026-32167 is a medium severity Microsoft vulnerability with a CVSS score of 6.7. 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

Medium

6.7

CVSS v3

<1%

EPSS, 30 days

Medium

Severity

Not in the CISA KEV catalog. EPSS exploit probability <1%. CVSS 6.7 (Medium).

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

Senserva AI Opinion for CVE-2026-32167

CVE-2026-32167 is an elevation of privilege flaw in Microsoft SQL Server that spans an unusually wide version range, from the current SQL Server 2025 (CU3) back to SQL Server 2017 (GDR), plus SQL Server 2022 (CU 24). Any org running these database engines is exposed, and the CVSS 8.8 rating reflects that a low privileged account could gain higher rights on the database host. It is not yet in CISA KEV and EPSS sits at 1 percent, so there is no confirmed exploitation, but the breadth of affected builds means patch coverage is easy to miss.

Do this: Inventory your SQL Server instances by version and apply the matching update (CU3, CU 24, or the 2017 GDR) starting with internet reachable or shared database servers.

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

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

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-32167 (source: https://senserva.com/cve/CVE-2026-32167.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-32167: Medium severity Microsoft vulnerability, CVSS 6.7
- EPSS 30-day exploitation probability: <1%
- Actively exploited (CISA KEV): no
- Fixed by: KB5083245, KB5083252, KB5084814, KB5084815, KB5084816, KB5084817, KB5084818, KB5084819, KB5084820, KB5084821
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 under 1%.

Fixed by KB5083245 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-32167

Lower priority: patch in your normal cycle. In Intune or Defender, confirm whether the fixing updates KB5083245, KB5083252, KB5084814, KB5084815, KB5084816, KB5084817, KB5084818, KB5084819, KB5084820, KB5084821 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-32167. 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.

KB5083245 KB5083252 KB5084814 KB5084815 KB5084816 KB5084817 KB5084818 KB5084819 KB5084820 KB5084821

Scope and sources

Affected products

Fixed by the same updates

CVE-2026-33120 CVE-2026-32176

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.