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

KB5084815

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

In short

Addresses three Important SQL Server vulnerabilities, including flaws that could enable privilege escalation or remote code execution. Linked-server queries using MSDASQL and a provider string might fail with error 7416.

Does it affect you? Applies to: SQL Server 2022 installations on the GDR servicing branch, on Windows or Linux. You need SQL Server 2022 or a SQL Server 2022 GDR release installed to apply the update.

Build
16.0.1175.1
Servicing branch
GDR
Security
3 fixed
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 3 changes

Linked Server

  • Addresses a flaw that could let a low-privileged SQL Server user gain sysadmin permissions through linked servers.1
    The vulnerability affects SQL Server linked servers on Linux and Windows.

Programmability

  • Resolves an issue where a specially crafted SQL query could make SQL Server stop responding.2
    An unprivileged user, including one with read-only permissions, could exploit the issue to cause a denial-of-service attack. Affects Linux and Windows.

SQL Agent

  • Resolves a SQL injection issue that could let an authorized attacker elevate privileges over a network.3
    The issue affects 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 that no login mapping exists. The Database Engine's stricter connection validation can reject certain configurations that worked in earlier builds.4

    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
KB5077465, KB5073031, KB5068407, KB5065221
+8 earlier KB5063756, KB5058712, KB5046861, KB5046057, KB5042211, KB5040936, KB5035432, KB5032968
Replaced by
KB5091158
VersionBuildChannel
2022 16.0.1175.1 General availability

Security

3 vulnerabilities fixed
3 important
VulnerabilitySeverityCVSS
CVE-2026-33120
Microsoft SQL Server Remote Code Execution Vulnerability
 Important 8.8
CVE-2026-32167
SQL Server Elevation of Privilege Vulnerability
 Important 6.7
CVE-2026-32176
SQL Server Elevation of Privilege Vulnerability
 Important 6.7

Downloads (Microsoft Update Catalog)

Package 2022
342.1 MB
sqlserver2022-kb5084815-x64.exe Main update · KB5084815 SHA-1: e6529067…0ce3f5

Updated components

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

Top changed componentsFiles
SQL Server Engine112
SQL Server PolyBase2

Sources

Updated
Cited passages from Microsoft's official notes (4)
  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 which a specially crafted SQL query triggers a fatal access violation that causes SQL Server to stop responding. support.microsoft.com
  3. 3. 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
  4. 4. 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, 4 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 5/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