Skip to the content
The Update Bureau
SQL Server 2016 SP3 + GDR SQL Server 2016 SP3 + GDR Security update
Patch Tuesday Final update for this version

KB5102340

KB5102340: Security update for SQL Server 2016, GDR branch, July 2026. Remote code execution flaw fixed; linked-server queries can fail

In short

The update fixes four vulnerabilities, including critical remote code execution vulnerability CVE-2026-54118. Linked-server queries using MSDASQL with a provider string can fail with error 7416.

Does it affect you? Applies to: SQL Server 2016 SP3 GDR installations on supported x64 systems. SQL Server 2016 SP3 or an earlier SQL Server 2016 SP3 GDR release is required.

Build
13.0.6500.1
Servicing branch
GDR
Security
4 fixed · 1 critical
Restart
Required

For servers on the GDR branch: they get security fixes only. Servers that install cumulative updates (CU branch) get a separate update. Which branch am I on?

What changes

Fixes 4 changes

Integration Services

  • Untrusted MSMQ messages can no longer use the affected deserialization path to cause remote code execution.1
    Restricts SoapFormatter deserialization in MessageQueueTask with an allow list binder. Applies to Windows.

Query Execution

  • The memory leak associated with using the input-buffer function or command is resolved.2
    Applies when using the sys.dm_exec_input_buffer dynamic management function or the DBCC INPUTBUFFER command. Linux and Windows.

Replication

  • Input passed to an internal replication procedure is checked and sanitized before the procedure uses it.3
    Addresses validation and sanitization of a parameter passed to an internal replication stored procedure. Linux and Windows.

SQL Agent

  • An SQL injection vulnerability that could let an authenticated attacker elevate privileges over a network is resolved.4
    Addresses improper neutralization of special elements in SQL Server commands. Linux and Windows.

Known issues

  1. Open Affects: Organizations and IT administrators

    Linked server queries that use MSDASQL fail with error 7416

    Linked-server queries using the MSDASQL provider and specifying a provider string (@provstr) can fail with error 7416, saying that no login mapping exists. Stricter Database Engine connection validation can reject certain configurations that worked in earlier builds.5

    Workaround status No workaround yet

    Microsoft has not published a manual workaround for this issue yet. Monitor release health until a resolving update is available.

Technical details

Data sheet · Security · Downloads · Components Click to collapse or expand

Data sheet

Released
2026-07-14
Classification
Security Updates
Type
Cumulative update
Servicing branch
GDR
Restart
Required
Replaces
KB5089271, KB5084821, KB5077474, KB5068401
+7 earlier KB5065226, KB5063762, KB5058718, KB5046855, KB5046063, KB5042207, KB5040946
VersionBuildChannel
2016 13.0.6500.1 General availability

Security

4 vulnerabilities fixed
1 critical 3 important
VulnerabilitySeverityCVSS
CVE-2026-54118
Microsoft SQL Server Remote Code Execution Vulnerability
 Critical 9.8
CVE-2026-47295
Microsoft SQL Server Elevation of Privilege Vulnerability
 Important 8.8
CVE-2026-55002
Microsoft SQL Server Elevation of Privilege Vulnerability
 Important 8.8
CVE-2026-47296
Microsoft SQL Server Elevation of Privilege Vulnerability
 Important 7.5

Downloads (Microsoft Update Catalog)

Package 2016
511.3 MB
sqlserver2016-kb5102340-x64.exe Main update · KB5102340 SHA-1: 35e5ef7a…7cb817

Updated components

517 files changed since the previous update for the same versions.

Top changed componentsFiles
SQL Server Engine77
SQL Server Analysis Services3

Sources

Updated
Cited passages from Microsoft's official notes (5)
  1. 1. This fix resolves an insecure deserialization vulnerability in MessageQueueTask by restricting SoapFormatter deserialization that uses an allow list binder. support.microsoft.com
  2. 2. This fix resolves a memory leak that occurs if the sys.dm_exec_input_buffer dynamic management function (DMF) or the DBCC INPUTBUFFER command is used. support.microsoft.com
  3. 3. This fix addresses input validation and sanitization of user input for a parameter that's passed to an internal replication stored procedure by validating and sanitizing the input before the stored procedure uses it. support.microsoft.com
  4. 4. This fix resolves an SQL injection vulnerability in SQL Server in which improper neutralization of special elements in SQL Server commands allows an authenticated attacker to elevate privileges over a network. support.microsoft.com
  5. 5. 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: support.microsoft.com
Checked automatically: 8 of 8 checks passed, 5 quoted passages · compared with Microsoft's page on Sep 26, 2026
  • Quotes found in the official pages: passed
  • Numbers found in the sources: passed
  • Vulnerabilities from the dossier only: passed
  • Links to allowed domains only: passed
  • Every official change covered: passed
  • Readable plain text: passed
  • Changes confirmed by the file list: passed
  • Sources agree: passed

A second AI read the text against the sources: correctness 5/5, clarity 4/5, completeness 5/5. How we work

Published by The Update Bureau. Written with AI from Microsoft's own documents, checked by rules and a second AI. How we work · Report a mistake