Skip to the content
The Update Bureau
SQL Server 2019 GDR SQL Server 2019 GDR Security update
Patch Tuesday

KB5084817

KB5084817: Security update for SQL Server 2019, GDR branch, April 2026. Linked-server security flaws fixed; MSDASQL queries can fail

In short

Fixes two Important SQL Server elevation-of-privilege vulnerabilities. Linked-server queries using MSDASQL might fail with error 7416 after installation.

Does it affect you? Applies to: SQL Server 2019 installations that have SQL Server 2019 itself or a SQL Server 2019 GDR release through this release installed. The package is for supported x64-based versions.

Build
15.0.2165.1
Servicing branch
GDR
Security
2 fixed
Restart
Required
Review notes Additional details from the official release notes (2) Read notes
  • This page The update fixes one linked-server elevation-of-privilege vulnerability and a separate SQL Agent SQL injection issue.
  • Known issues This issue affects SQL Server users whose linked-server queries use MSDASQL and specify a provider string; it is not a general issue for all readers.

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

For: SQL Server users on Linux and Windows

  • Addresses a linked-server vulnerability that could let a low-privileged SQL Server user gain sysadmin permissions.1
    Bug reference 5029941; applies to Linux and Windows.

SQL Agent

For: SQL Server users on Windows

  • Resolves an issue where SQL injection could let an authorized attacker elevate privileges over a network.2
    Bug reference 4999190; Windows.

Known issues

  1. Open Affects: Everyone

    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, even if they worked on earlier builds.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
GDR
Restart
Required
Replaces
KB5077470, KB5068405, KB5065223, KB5063758
+6 earlier KB5058713, KB5046859, KB5046056, KB5042214, KB5040986, KB5035434
Replaced by
KB5090408
VersionBuildChannel
2019 15.0.2165.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

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

Top changed componentsFiles
SQL Server Engine118
SQL Server PolyBase4

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 3/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