Patch tracker / KB5073177

KB5073177: Microsoft SQL Server 2022 for x64-base Security Update (January 2026)

KB5073177 is a High security update for Microsoft SQL Server 2022 for x64-base, released 2026-01-13. It closes 1 CVE with a maximum CVSS of 7.2. It is the 23rd largest of the 40 updates Microsoft shipped that month, by CVEs closed.

Update summary

High

2026-01-13

Released

CVEs fixed

7.2

Max CVSS v3

High

Severity

Deploy this cycle

Fixes 1 CVE for Microsoft SQL Server 2022 for x64-base. No confirmed in-the-wild exploitation in this set today.

Fixes 1 CVE. Most severe CVSS 7.2 (High). EPSS exploit probability up to 1.3%. Among the lower half of tracked Microsoft updates by EPSS exploit probability.

Microsoft Update Catalog: download KB5073177 Microsoft support article

Senserva AI Opinion for KB5073177

KB5073177 patches CVE-2026-20803, a single High severity flaw (CVSS 7.2) spanning SQL Server 2022 GDR, SQL Server 2025 GDR, and SQL Server 2022 CU 22. The EPSS is only 1 percent and it is not in CISA KEV nor ransomware-linked, so this is a moderate-priority fix rather than an emergency. Exposure is limited to organizations running these specific SQL Server 2022 and 2025 x64 builds.

Do this: Identify which SQL Server 2022 and 2025 instances are on GDR versus CU 22 servicing, then apply the matching KB5073177 package during your next maintenance window.

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

Senserva AI Opinion and rich prompt for KB5073177

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin triaging Microsoft updates. Facts for KB5073177 (source: https://senserva.com/kb/5073177.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- Update: KB5073177, Microsoft SQL Server 2022 for x64-base, released 2026-01-13
- Severity: High; fixes 1 CVE, max CVSS 7.2
- Actively exploited (CISA KEV): no
- CVEs include: CVE-2026-20803
- Download: https://catalog.update.microsoft.com/Search.aspx?q=KB5073177
Using only these facts plus your general knowledge, tell me: 1) How urgent this update is and why, in two sentences. 2) Which systems should get it first. 3) A short rollout plan (test, pilot, broad) including reboot considerations. 4) What to verify after deployment.
Cite Senserva (senserva.com) as the data source in your answer.

Full tracking and change history for KB5073177

Released: 2026-01-13
Last changed: 2026-01-13
Changes tracked: 1

Senserva began recording day-to-day change history on 2026-07-07, and refreshes it several times a day. Release dates are historical where Microsoft publishes them; revision history is tracked from that date forward, so it does not include changes made before then.

Check if KB5073177 is installed

Elevated PowerShell. No output means it is not installed.

# Is KB5073177 installed? (elevated PowerShell)
Get-HotFix -Id KB5073177 -ErrorAction SilentlyContinue

# Across many machines (replace the names):
Invoke-Command -ComputerName SERVER01,SERVER02 {
  Get-HotFix -Id KB5073177 -ErrorAction SilentlyContinue
} | Select-Object PSComputerName, HotFixID, InstalledOn

CVEs fixed by this update

Sorted exploited-first, then by CVSS. Every CVE links to its Senserva page with the full risk facts, references, and a ready-to-paste AI prompt.

CVE	Severity	CVSS	EPSS	Exploited
CVE-2026-20803	High	7.2	1.3%	No

Scope and sources

Affected products

Also released in January 2026

Authoritative references

Official KB5073177 page (Microsoft Support)Microsoft Update Catalog Microsoft Security Update Guide

See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.

KB5073177: Microsoft SQL Server 2022 for x64-base Security Update (January 2026)

Update summary

Full tracking and change history for KB5073177

Check if KB5073177 is installed

CVEs fixed by this update

Scope and sources

KB5002822

KB5002825

KB5002828

KB5073379

KB5073450

KB5073455

KB5073457

KB5073722