Skip to the content
The Update Bureau
SQL Server 2025 CU3 + GDR SQL Server 2025 CU3 + GDR Security update
Patch Tuesday

KB5083245

KB5083245: Security update for SQL Server 2025, CU branch, April 2026. Linked-server privilege flaw fixed; MSDASQL queries can fail

In short

The update fixes two SQL Server vulnerabilities, including a linked-server privilege issue. Linked-server queries using MSDASQL and a provider string might fail with error 7416.

Does it affect you? Applies to: SQL Server 2025 on Windows and Linux, all editions.

Build
17.0.4030.1
Servicing branch
CU
Security
2 fixed
Restart
Required
Review notes Additional details from the official release notes (2) Read notes
  • In detail The page identifies both CVEs as SQL Server elevation-of-privilege vulnerabilities, but does not state which CVE corresponds to the linked-server fix.
  • Known issues The issue concerns certain SQL Server linked-server configurations using MSDASQL and a provider string; it does not affect everyone.

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

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

  • A linked-server privilege vulnerability is addressed. It could let a low-privileged SQL Server user gain sysadmin permissions.1
    Applies to SQL Server on Linux and Windows.

SQL Agent

  • An SQL injection vulnerability that could let an authorized attacker elevate privileges over a network is resolved.2
    Applies to SQL Server on Windows.

Known issues

  1. Open Affects: Everyone

    Linked server queries that use MSDASQL fail with error 7416

    Linked-server queries using the MSDASQL provider and a provider string might fail with error 7416, reporting that no login mapping exists. The Database Engine's stricter connection validation can reject certain configurations that worked in earlier builds.3

    How to apply the workaround Workaround

    Use the workaround guidance in the linked Microsoft troubleshooting article.3

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
KB5077896, KB5077466, KB5075211, KB5078298
Replaced by
KB5089899
VersionBuildChannel
2025 17.0.4030.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

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

Top changed componentsFiles
SQL Server Engine111
SQL Server PolyBase2

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. For more information and workarounds, see Linked server queries that use MSDASQL fail with error 7416. 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 4/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