Patch tracker / KB5102337

KB5102337: SQL Server 2017 Security Update (July 2026)

KB5102337 is a Critical security update for SQL Server 2017, released 2026-07-14. It closes 4 CVEs with a maximum CVSS of 9.8. Microsoft documents 1 known issue for this update, quoted below.

Before you deploy: Microsoft lists 1 known issue for this update.

Linked server queries that use MSDASQL fail with error 7416

Known issues

Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.

Update summary

Critical

2026-07-14

Released

CVEs fixed

9.8

Max CVSS v3

Critical

Severity

Deploy this cycle

Fixes 4 CVEs for SQL Server 2017. No confirmed in-the-wild exploitation in this set today.

Fixes 4 CVEs. Most severe CVSS 9.8 (Critical). EPSS exploit probability up to 1.5%. Among the lower half of tracked Microsoft updates by EPSS exploit probability.

Senserva found thiswe track every release for this product line, so we can tell you this package is behind

A newer security update for Microsoft SQL Server 2017 for x64-based Systems (CU 31) has shipped since this one: KB5122774 (2026-09-08). For cumulative update families the newer package includes these fixes, so installing that one is usually the shorter path. Verify against your own update rings before you skip this package.

Senserva found thisread these before you deploy broadly

Microsoft documents 1 known issue with this update.

Linked server queries that use MSDASQL fail with error 7416

The full text, quoted from Microsoft

Microsoft Update Catalog: download KB5102337 Microsoft support article

Senserva AI Opinion for KB5102337

KB5102337 is Cumulative Update 31 for SQL Server 2017 on x64 systems, shipping as a Security Update in the July 2026 cycle. The MSRC release document maps no named zero-days to this update, and per-update CVE detail is still provisional because Microsoft has not published it for this cycle. Exposure is limited to database servers still running the SQL Server 2017 branch, which are often internally facing and less frequently patched than OS layers.

Do this: Inventory your SQL Server 2017 x64 instances and schedule CU 31 (KB5102337) through a test instance before applying to production database servers.

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

Senserva AI Opinion and rich prompt for KB5102337

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 KB5102337 (source: https://senserva.com/kb/5102337.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed daily (early morning US Central)):
- Update: KB5102337, SQL Server 2017, released 2026-07-14
- Severity: Critical; fixes 4 CVEs, max CVSS 9.8
- Actively exploited (CISA KEV): no
- CVEs include: CVE-2026-47295, CVE-2026-47296, CVE-2026-54118, CVE-2026-55002
- Download: https://catalog.update.microsoft.com/Search.aspx?q=KB5102337
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 KB5102337

Released: 2026-07-14
Last changed: 2026-09-26
Changes tracked: 4

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 KB5102337 is installed

Elevated PowerShell. No output means it is not installed.

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

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

Known issues, from Microsoft

Quoted from Microsoft's support article for KB5102337 (checked 2026-10-05). Microsoft lists 1 known issue. Verify against the article before acting.

Linked server queries that use MSDASQL fail with error 7416

Linked server queries that use the MSDASQL (OLE DB Provider for ODBC Drivers) provider and specify a provider string ( @provstr ) fail and return the following error message:

Msg 7416, Level 16

Access to the remote server is denied because no login-mapping exists.

A stricter connection validation check in the Database Engine can reject connections for certain linked server configurations that use the MSDASQL provider, even if earlier builds allowed those connections.

For more information and workarounds, see Linked server queries that use MSDASQL fail with error 7416 .

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-54118	Critical	9.8	1.5%	No
CVE-2026-47295	High	8.8	<1%	No
CVE-2026-55002	High	8.8	<1%	No
CVE-2026-47296	High	7.5	<1%	No

Scope and sources

Affected products

Microsoft SQL Server 2017 for x64-based Systems (CU 31)

Also released in July 2026

Authoritative references

Official KB5102337 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.

KB5102337: SQL Server 2017 Security Update (July 2026)

Update summary

Full tracking and change history for KB5102337

Check if KB5102337 is installed

Known issues, from Microsoft

Linked server queries that use MSDASQL fail with error 7416

CVEs fixed by this update

Scope and sources

KB5099444

KB5099445

KB5099535

KB5099536

KB5099538

KB5099539

KB5099540

KB5101649