KB5122772: Security update for SQL Server 2019, CU branch, September 2026. 52 vulnerabilities addressed; linked-server queries can fail
Addresses 52 vulnerabilities, including three Critical remote code execution flaws; none are listed as exploited. Some linked-server queries might fail with error 7416 after installation.
Does it affect you? Applies to: SQL Server 2019 instances on supported x64 Windows systems, with SQL Server 2019 or a CU through CU32 GDR installed. Linux users can update through the SQL Server 2019 cumulative update repository and package instructions.
Review notes Additional details from the official release notes (2) Read notes
- Known issues The error affects linked-server queries that use the MSDASQL provider and specify a provider string. It does not apply to all linked-server connections.
- In short KB5128494 superseded KB5122772 on October 16, 2026.
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 36 changes
PolyBase
For: SQL Server administrators on Linux and Windows
-
PolyBase handles unsafe data more safely.1
Addresses unsafe deserialization in the SQL Server PolyBase Engine.
-
PolyBase services no longer open certain direct network connections when started with modified command-line settings.19
Prevents PolyBase services from opening raw TCP listeners for the DW Engine and DMS control and data channels when modified command-line parameters activate the deprecated feature.
Backup Restore
-
Managed backup procedures get a security fix.2
Addresses a vulnerability affecting
managed_backup.sp_get_encryption_optionandmanaged_backup.sp_do_backup; customers using managed backup should apply the update through standard SQL Server servicing. -
Invalid or incomplete backup details are rejected safely.3
Improves internal validation of backup metadata processed by the SQL Server Volume Shadow Copy Service (VSS) Writer.
SQL Agent
-
SQL Server Agent applies stronger checks when loading task components.4
Strengthens security validation when SQL Server Agent loads task-agent components.
-
SQL Server Agent handles certain inputs more reliably and securely.5
Addresses reliability and security issues when SQL Server Agent processes specific input.
-
SQL Server Agent gets security and reliability fixes for certain operating conditions.15
Addresses an issue affecting SQL Server Agent security and reliability under specific operating conditions.
WMI Management Provider (SqlMgmProvider)
For: SQL Server administrators on Windows
-
The SQL WMI Provider handles malformed input correctly while retaining its behavior for valid input.6
Fixes incorrect processing of malformed input by the SQL WMI Provider.
Security Infrastructure
For: SQL Server administrators on Linux and Windows
-
SQL Server's Microsoft Entra sign-in handling gets a security fix.7
Addresses a security vulnerability in Microsoft Entra authentication login handling.
SQL Connectivity
For: SQL Server administrators on Windows
-
SQL Server handles malformed network data with invalid length values more safely.8
Addresses validation of malformed Tabular Data Stream (TDS) and Binary XML input processed by SQL Server components.
Replication
-
Replication procedures handle supplied and stored identifiers correctly.9
Addresses identifier handling and input validation in replication stored procedures.
-
Replication procedures handle longer or unusual identifiers correctly.10
Fixes replication stored procedures that incorrectly process identifiers containing longer or special characters.
-
Replication procedures handle identifiers with special characters correctly.11
Fixes replication stored procedures that incorrectly process identifiers containing special characters.
-
A merge replication procedure checks supplied information more reliably.12
Improves input validation for a merge replication metadata stored procedure.
-
A replication procedure handles a supplied path correctly.13
Addresses a replication stored procedure that handles a caller-supplied path value.
-
Replication procedures check supplied values more reliably.14
Improves input validation for parameters used by replication stored procedures.
-
A replication lookup no longer reads arbitrary memory.27
Addresses an issue in which the class ID lookup call reads arbitrary memory.
-
Replication checks the limits of embedded attestation information.28
Adds bounds validation for embedded attestation fields.
-
Replication handles malformed or malicious stored data more safely.29
Strengthens Object Store Format (OSF) deserialization against malformed or malicious stream data.
-
Replication checks data lengths inside protected code more reliably.30
Strengthens buffer length validation checks within enclave code.
-
A replication lookup no longer reads arbitrary memory.32
Addresses an issue in which the class ID lookup call reads arbitrary memory.
-
Replication better protects internal data while processing it.34
Addresses an issue affecting the protection of internal replication data during processing operations.
-
Merge Replication handles text data correctly during processing.35
Addresses an issue in Merge Replication affecting the handling of text data during processing operations.
-
Replication gets stronger checks for safer and more reliable processing.36
Addresses an issue in replication operations affecting validation and handling to enhance security and reliability.
In-Memory OLTP
For: SQL Server administrators on Linux and Windows
-
A text-processing function no longer reads past its allocated memory when handling certain malformed text in a compiled database procedure.16
Addresses
SUBSTRINGreading beyond the allocated buffer while processing malformed double-byte character set (DBCS)varcharinput in a natively compiled In-Memory OLTP procedure. -
Converting or shortening certain text in a compiled database procedure no longer causes the server to stop responding.17
Addresses an access violation when converting or truncating an
NVARCHARvalue containing an Ideographic Variation Sequence (IVS) under a Variation Selector Sensitive (_VSS) collation in a natively compiled In-Memory OLTP procedure. -
Streaming large text from a compiled procedure no longer overwrites memory in certain conditions that could stop the server.18
Fixes a heap buffer overwrite when a natively compiled stored procedure streams
nvarchar(max)data withSET TEXTSIZEtruncation under a Variation Selector Sensitive (_VSS) collation and uses small TDS packet sizes.
XML
For: SQL Server administrators on Linux and Windows
-
A query with an extremely large plan description no longer causes SQL Server to stop unexpectedly.20
Addresses an access violation when processing a query with an extremely large
OPTION (USE PLAN)XML declaration. -
SQL Server handles a type of XML attribute list correctly.23
Addresses an XML data type handling bug in Document Type Definition (DTD) attribute lists.
-
A specially crafted XML file no longer causes SQL Server to stop responding or terminate unexpectedly when imported.24
Fixes an integer overflow in the SQL Server XML reader when processing a specially crafted XML format file through
OPENROWSET(BULK...)orBULK INSERT.
Programmability
-
SQL Server processes and displays certain internal event information more securely.21
Updates how SQL Server processes and outputs certain internal event data to help protect information.
-
A data-writing method gets a fix for a memory-write issue that could affect availability or security when the common language runtime is enabled.33
Addresses improper field offset validation in
SqlDataRecord.SetBytesforsql_variantvalues; prevents an out-of-bounds heap write that could cause denial of service or elevation of privilege when CLR is enabled.
Extended Events
For: SQL Server administrators on Linux and Windows
-
Extended Events gets a security fix for a problem that could damage memory.22
Addresses insufficient validation in Extended Events that can cause memory corruption.
-
Reading a specially crafted event file no longer exposes information or causes a denial of service.25
Resolves several security vulnerabilities triggered when the database engine reads a specially crafted Extended Events (
.xel) file.
Query Execution
For: SQL Server administrators on Linux and Windows
-
An authenticated user can no longer use invalid input to disclose a limited amount of memory.26
Strengthens input validation to address improper validation that could allow an authenticated user to disclose a limited amount of memory.
-
Invalid input from an authenticated user can no longer trigger memory-read problems that might create a dump file or cause low-memory conditions.31
Strengthens input validation for an issue where SQL Server dereferences and reads, but does not execute, a pointer provided by an authenticated user.
Improvements 4 changes
Replication
-
Replication procedures get stronger internal checks.37
Improves validation and security checks for replication stored procedures so operations use the expected safeguards.
-
Queued Updating Subscriptions in Transactional Replication get security and reliability improvements.38
Includes security and reliability improvements for Queued Updating Subscriptions in Transactional Replication.
-
Queued Updating Subscriptions in Transactional Replication get security and reliability improvements.39
Includes security and reliability improvements for Queued Updating Subscriptions in Transactional Replication.
Query Store
For: SQL Server administrators on Windows
-
Showplan handles input more securely and reliably.40
Improves the handling of input to Showplan to enhance security and reliability.
Known issues
-
Linked server queries that use MSDASQL fail with error 7416
Queries that use a configured connection from SQL Server to another server can fail with error 7416, even if earlier builds allowed them.41
Workaround status No workaround yetMicrosoft 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-09-08
- Classification
- Security Updates
- Type
- Cumulative update
- Servicing branch
- CU
- Restart
- Required
- Replaces
- KB5102335, KB5090407, KB5084816, KB5077469
- Replaced by
- KB5128494
| Version | Build | Channel |
|---|---|---|
| 2019 | 15.0.4490.9 | General availability |
Security
| Vulnerability | Severity | CVSS |
|---|---|---|
|
Microsoft SQL Server Remote Code Execution Vulnerability
|
Critical | 9.8 |
|
Microsoft SQL Server Remote Code Execution Vulnerability
|
Critical | 9.0 |
|
Microsoft SQL Server Remote Code Execution Vulnerability
|
Critical | 9.0 |
The table lists the 3 exploited, publicly disclosed or critical vulnerabilities. See all 52 vulnerabilities →
Downloads (Microsoft Update Catalog)
Updated components
158 files changed since the previous update for the same versions.
| Top changed components | Files |
|---|---|
| SQL Server Engine | 119 |
| SQL Server PolyBase | 4 |
Verified in package: changed files confirm PolyBase.
Sources
Cited passages from Microsoft's official notes (41)
-
1.
This fix addresses an unsafe deserialization in SQL Server PolyBase Engine.
support.microsoft.com -
2.
This fix addresses a vulnerability that affects the SQL Server managed backup to the Microsoft Azure stored procedures,
support.microsoft.commanaged_backup.sp_get_encryption_optionandmanaged_backup.sp_do_backup. -
3.
This fix addresses an issue in which internal validation of backup metadata that's processed by the SQL Server Volume Shadow Copy Service (VSS) Writer improves handling of malformed or undersized metadata to ensure that it's rejected safely.
support.microsoft.com -
4.
This fix addresses a security validation issue in SQL Server Agent if SQL Server Agent loads task-agent components.
support.microsoft.com -
5.
This fix addresses reliability and security issues in SQL Server Agent if it processes specific input.
support.microsoft.com -
6.
This fix addresses an issue in which the SQL WMI Provider processes malformed input incorrectly while preserving existing behavior for valid input.
support.microsoft.com -
7.
This fix addresses a security vulnerability in Microsoft Entra authentication login handling in SQL Server.
support.microsoft.com -
8.
This fix addresses validation of malformed Tabular Data Stream (TDS) and Binary XML input processed by SQL Server components.
support.microsoft.com -
9.
This fix addresses identifier handling and input validation in replication stored procedures to ensure that supplied and stored values are processed correctly.
support.microsoft.com -
10.
This fix addresses replication stored procedures that incorrectly process identifiers that contains longer or special characters.
support.microsoft.com -
11.
This fix addresses replication stored procedures that incorrectly process identifiers that contain special characters.
support.microsoft.com -
12.
This fix addresses input validation for a merge replication metadata stored procedure to ensure that supplied values are processed reliably.
support.microsoft.com -
13.
This fix addresses a replication stored procedure that handles a caller-supplied path value.
support.microsoft.com -
14.
This fix addresses input validation for parameters that are used by replication stored procedures to ensure that supplied values are processed reliably.
support.microsoft.com -
15.
This fix addresses an issue that affects the security and reliability of SQL Server Agent under specific operating conditions.
support.microsoft.com -
16.
This fix addresses an issue in which the SUBSTRING function reads beyond the allocated buffer if it processes malformed double-byte character set (DBCS) varchar input.
support.microsoft.com -
17.
This fix addresses an issue in which converting or truncating an NVARCHAR value that contains an Ideographic Variation Sequence (IVS) under a Variation Selector Sensitive (_VSS) collation causes an access violation.
support.microsoft.com -
18.
This fix addresses an issue in which a natively compiled stored procedure causes a heap buffer overwrite while streaming nvarchar(max) data that has SET TEXTSIZE truncation under a Variation Selector Sensitive (_VSS) collation.
support.microsoft.com -
19.
The fix prevents PolyBase services from opening raw TCP listeners for the DW Engine and DMS control and data channels if the services start by having modified command-line parameters.
support.microsoft.com -
20.
This fix addresses an access violation that occurs if SQL Server processes a query that has an extremely large OPTION (USE PLAN) XML declaration.
support.microsoft.com -
21.
This fix addresses a security issue in SQL Server by updating how SQL Server processes, and outputs certain internal event data to help protect information.
support.microsoft.com -
22.
This fix addresses a security issue in SQL Server in which insufficient validation in Extended Events can cause memory corruption.
support.microsoft.com -
23.
This fix addresses an XML data type handling bug in Document Type Definition (DTD) attribute lists.
support.microsoft.com -
24.
This fix addresses an integer overflow in the SQL Server XML reader that occurs if SQL Server processes a specially crafted XML format file through
support.microsoft.comOPENROWSET(BULK...)orBULK INSERT. -
25.
This fix resolves several security vulnerabilities that allow information disclosure or a denial of service if the database engine reads a specially crafted Extended Events (.xel) file.
support.microsoft.com -
26.
This fix addresses an improper input validation issue in SQL Server that allows an authenticated user to disclose a limited amount of memory.
support.microsoft.com -
27.
This fix addresses an issue in which the class ID lookup call reads arbitrary memory.
support.microsoft.com -
28.
This fix adds bounds validation for embedded attestation fields.
support.microsoft.com -
29.
This fix strengthens Object Store Format (OSF) deserialization against malformed or malicious stream data.
support.microsoft.com -
30.
This fix strengthens buffer length validation checks within enclave code.
support.microsoft.com -
31.
This fix addresses an improper input validation issue in SQL Server in which an authenticated user can provide a pointer that SQL Server dereferences and reads but does not execute.
support.microsoft.com -
32.
This fix addresses an issue in which the class ID lookup call reads arbitrary memory.
support.microsoft.com -
33.
This fix addresses improper field offset validation in the SqlDataRecord.SetBytes API for sql_variant values.
support.microsoft.com -
34.
This fix addresses an issue that affects the protection of internal replication data during processing operations.
support.microsoft.com -
35.
This fix addresses an issue in Merge Replication that affects the handling of text data during processing operations.
support.microsoft.com -
36.
This fix addresses an issue in replication operations that affects validation and handling to enhance security and reliability.
support.microsoft.com -
37.
This fix improves internal validation and security checks for SQL Server replication stored procedures to ensure that replication operations are processed by using the expected security safeguards.
support.microsoft.com -
38.
This update includes security and reliability improvements for the Queued Updating Subscriptions in Transactional Replication.
support.microsoft.com -
39.
This update includes security and reliability improvements for the Queued Updating Subscriptions in Transactional Replication.
support.microsoft.com -
40.
This fix improves the handling of input to Showplan to enhance security and reliability.
support.microsoft.com -
41.
Linked server queries that use the
support.microsoft.comMSDASQL(OLE DB Provider for ODBC Drivers) provider and specify a provider string (@provstr) fail and return the following error message:
Checked automatically: 8 of 8 checks passed, 41 quoted passages · compared with Microsoft's page on Nov 8, 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 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