KB5084821: Security update for SQL Server 2016, GDR branch, April 2026. MSDASQL linked-server queries fail with error 7416
The update addresses two SQL Server elevation-of-privilege vulnerabilities. Linked-server queries using MSDASQL with a provider string fail with error 7416.
Does it affect you? Applies to: Devices running the x64 version of SQL Server 2016 SP3 GDR. The listed fixes affect SQL Server on Linux and Windows, and SQL Agent on Windows.
Review notes Additional details from the official release notes (4) Read notes
- This page The stricter connection check can reject some linked-server configurations that use MSDASQL and a provider string; it does not say that every such query fails.
- In short The stricter connection check can reject some linked-server configurations that use MSDASQL and a provider string; it does not say that every such query fails.
- In detail The stricter connection check can reject some linked-server configurations that use MSDASQL and a provider string; it does not say that every such query fails.
- Known issues The stricter connection check can reject some linked-server configurations that use MSDASQL and a provider string; it does not say that every such query fails.
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 2 changes
Linked Server
-
Addresses a vulnerability that could let a low-privileged SQL Server user gain sysadmin permissions through linked servers.1
Applies to SQL Server on Linux and Windows.
SQL Agent
-
Resolves a SQL injection issue that could let an authorized attacker elevate privileges over a network.2
Applies to SQL Server on Windows.
Known issues
-
Linked server queries that use MSDASQL fail with error 7416
Linked-server queries that use the MSDASQL provider and specify a provider string fail with error 7416: access to the remote server is denied because no login-mapping exists.3
Workaround 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-04-14
- Classification
- Security Updates
- Type
- Cumulative update
- Servicing branch
- GDR
- Restart
- Required
- Replaces
- KB5077474, KB5068401, KB5065226, KB5063762
- Replaced by
- KB5089271
| Version | Build | Channel |
|---|---|---|
| 2016 | 13.0.6485.1 | General availability |
Security
| Vulnerability | Severity | CVSS |
|---|---|---|
|
SQL Server Elevation of Privilege Vulnerability
|
Important | 6.7 |
|
SQL Server Elevation of Privilege Vulnerability
|
Important | 6.7 |
Downloads (Microsoft Update Catalog)
Updated components
514 files changed since the previous update for the same versions.
| Top changed components | Files |
|---|---|
| SQL Server Engine | 77 |
| SQL Server Analysis Services | 3 |
Sources
Cited passages from Microsoft's official notes (3)
-
1.
This fix addresses an elevation of privilege vulnerability in SQL Server linked servers that allows a low-privileged SQL Server user to gain sysadmin permissions.
support.microsoft.com -
2.
This fix resolves an issue in SQL Server in which improper neutralization of special elements in SQL commands (SQL injection) allows an authorized attacker to elevate privileges over a network.
support.microsoft.com -
3.
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, 3 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 3/5, clarity 4/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