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

KB5083252

KB5083252: Security update for SQL Server 2022, CU branch, April 2026. Linked-server privilege flaw addressed; MSDASQL queries can fail

In short

Addresses two important SQL Server elevation-of-privilege vulnerabilities. Linked-server queries using MSDASQL can fail with error 7416 after the update.

Does it affect you? Applies to: SQL Server 2022 installations with SQL Server 2022 or a CU through CU24 GDR installed. The listed fixes cover Windows and Linux; the downloadable package is x64.

Build
16.0.4250.1
Servicing branch
CU
Security
2 fixed
Restart
Required

For servers on the CU branch: they install cumulative updates, which also bring 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

Verified in package

For: SQL Server instances on Linux and Windows

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

SQL Agent

Verified in package

For: SQL Server instances on Windows

  • Resolves a SQL injection issue that could let an authorized attacker elevate privileges over a network.2
    Bug reference 5052462; SQL Server Engine. The fix applies to 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 MSDASQL and specify a provider string can fail with error 7416, reporting that 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
CU
Restart
Required
Replaces
KB5080999, KB5077464, KB5078297, KB5072936
+22 earlier KB5068450, KB5068406, KB5065865, KB5065220, KB5063814, KB5059390, KB5058721, KB5054531, KB5050771, KB5048038, KB5048033, KB5046862, KB5046059, KB5041321, KB5042578, KB5038325, KB5040939, KB5036432, KB5036343, KB5033663, KB5032679, KB5033592
Replaced by
KB5089900
VersionBuildChannel
2022 16.0.4250.1 General availability

Security

2 vulnerabilities fixed
2 important
VulnerabilitySeverityCVSS
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
464.4 MB
sqlserver2022-kb5083252-x64.exe Main update · KB5083252 SHA-1: bd07a024…be5899

Updated components

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

Top changed componentsFiles
SQL Server Engine112
SQL Server PolyBase3

Verified in package: changed files confirm Linked Server, SQL Agent.

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