KB5102338: Security update for SQL Server 2017, GDR branch, July 2026. Critical remote-code flaw; MSDASQL linked-server queries can fail
Fixes four vulnerabilities, including a critical SQL Server remote-code execution flaw. Linked-server queries using MSDASQL with a provider string might fail with error 7416.
Does it affect you? Applies to: Supported x64 systems running SQL Server 2017, including installations on the GDR branch.
Review notes Additional details from the official release notes (1) Read note
- This page Linked-server queries that use MSDASQL and specify a provider string fail with error 7416.
The official sources are linked at the end of the page.
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
-
MessageQueueTask blocks remote code execution from an untrusted Microsoft Message Queuing message by restricting unsafe deserialization.1
Restricts
SoapFormatterdeserialization with an allow list binder.
Query Execution
-
Fixes a memory leak that can occur when the input buffer is queried.2
The leak occurs when using the
sys.dm_exec_input_bufferdynamic management function or theDBCC INPUTBUFFERcommand.
Replication
-
Input passed to an internal replication procedure is validated and sanitized before the procedure uses it.3
Addresses validation and sanitization of user input passed to an internal replication stored procedure.
SQL Agent
-
Fixes a SQL injection vulnerability that could let an authenticated attacker elevate privileges over a network.4
Resolves improper neutralization of special elements in SQL Server commands.
Known issues
-
Linked server queries that use MSDASQL fail with error 7416
Linked-server queries that use the
MSDASQLprovider and specify a provider string (@provstr) might fail with error 7416: access to the remote server is denied because no login-mapping exists.5Workaround status No workaround yetMicrosoft 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
- KB5090347, KB5084819, KB5077472, KB5068403
- Replaced by
- KB5122775
| Version | Build | Channel |
|---|---|---|
| 2017 | 14.0.2120.1 | General availability |
Security
| Vulnerability | Severity | CVSS |
|---|---|---|
|
Microsoft SQL Server Remote Code Execution Vulnerability
|
Critical | 9.8 |
|
Microsoft SQL Server Elevation of Privilege Vulnerability
|
Important | 8.8 |
|
Microsoft SQL Server Elevation of Privilege Vulnerability
|
Important | 8.8 |
|
Microsoft SQL Server Elevation of Privilege Vulnerability
|
Important | 7.5 |
Downloads (Microsoft Update Catalog)
Updated components
114 files changed since the previous update for the same versions.
| Top changed components | Files |
|---|---|
| SQL Server Engine | 91 |
Sources
Cited passages from Microsoft's official notes (5)
-
1.
This fix resolves an insecure deserialization vulnerability in MessageQueueTask by restricting SoapFormatter deserialization that uses an allow list binder.
support.microsoft.com -
2.
This fix resolves a memory leak that occurs if the
support.microsoft.comsys.dm_exec_input_bufferdynamic management function (DMF) or the DBCC INPUTBUFFER command is used. -
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.
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.
Linked server queries that use the
support.microsoft.comMSDASQL(OLE DB Provider for ODBC Drivers) provider and specify a provider string (@provstr) fail and return the following error message:
Checked automatically: 8 of 8 checks passed, 5 quoted passages · compared with Microsoft's page on Oct 16, 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 4/5, clarity 3/5, completeness 4/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