Skip to the content
The Update Bureau
SQL Server 2016 SP3 AC + GDR SQL Server 2016 SP3 AC + GDR Security update
Patch Tuesday

KB5084820

KB5084820: Security update for SQL Server 2016, Azure Connect Feature Pack branch, April 2026. Linked-server privilege flaw addressed; MSDASQL queries fail

In short

The update addresses two SQL Server elevation-of-privilege vulnerabilities. Linked-server queries using MSDASQL with a provider string might fail with error 7416.

Does it affect you? Applies to: This update applies to x64 installations of SQL Server 2016 SP3 with the Azure Connect Feature Pack installed.

Build
13.0.7080.1
Servicing branch
Azure Connect Feature Pack
Security
2 fixed
Restart
Required
Review notes Additional details from the official release notes (1) Read note
  • This page The issue affects certain linked-server configurations using MSDASQL with a provider string; it does not mean all MSDASQL queries fail.

The official sources are linked at the end of the page.

For servers on the Azure Connect Feature Pack of Service Pack 3, the branch with fixes beyond security. Servers on the GDR branch (security fixes only) get a separate update. Which branch am I on?

What changes

Fixes 2 changes

Linked Server

  • Addresses a linked-server vulnerability that could let a low-privileged SQL Server user gain sysadmin permissions.1
    The fix 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
    The fix applies to SQL Agent on Windows.

Known issues

  1. Open Affects: Organizations and IT administrators

    Linked server queries that use MSDASQL fail with error 7416

    Linked-server queries that use the MSDASQL provider and specify a provider string might fail with error 7416, saying no login mapping exists.3

    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-04-14
Classification
Security Updates
Type
Cumulative update
Servicing branch
Azure Connect Feature Pack
Restart
Required
Replaces
KB5077473, KB5068400, KB5065227, KB5063761
+5 earlier KB5058717, KB5046856, KB5046062, KB5042209, KB5040944
Replaced by
KB5089270
VersionBuildChannel
2016 13.0.7080.1 General availability

Security

2 vulnerabilities fixed
2 important
VulnerabilitySeverityCVSS
SQL Server Elevation of Privilege Vulnerability
Important 6.7
SQL Server Elevation of Privilege Vulnerability
Important 6.7

Downloads (Microsoft Update Catalog)

Updated components

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

Top changed componentsFiles
SQL Server Engine77

Sources

Updated
Cited passages from Microsoft's official notes (3)
  1. 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. 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. 3. 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, 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 4/5, clarity 3/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