Skip to main content
Mallory
← Back to News
patch-regressionwidely-deployed-product-advisory

SQL Server 2022 Update Fixes 33 Vulnerabilities but Introduces Recovery-Query Regression

Patch & Detection Intelligence · 5 sources · Updated 4d ago · First seen Nov 11, 2026

SQL Server 2022 Update Fixes 33 Vulnerabilities but Introduces Recovery-Query Regression

Microsoft released security update KB5129300 for SQL Server 2022 CU27, bringing the product to version 16.0.4315.2. Its November 10 advisory lists 33 vulnerabilities: 12 remote-code-execution flaws, 12 elevation-of-privilege flaws, and nine information-disclosure flaws. Fixes address memory safety, authorization, and input validation across replication, SQL Server Integration Services, connectivity, and other database components. The update also disables XSLT scripting by default. Microsoft’s notice provides neither vulnerability severity scores nor information about active exploitation. Third-party tracker Senserva reports 54 CVEs and a maximum CVSS score of 9.8, figures not corroborated by the supplied Microsoft notices.

Microsoft also identifies a regression that can trigger an access violation when sys.dm_exec_requests is queried during database recovery. While investigating a fix, Microsoft lists trace flag 4696, avoiding affected queries, or uninstalling the update as temporary mitigations. Administrators should test recovery and monitoring workflows before broad deployment, assess dependencies on XSLT scripting, and plan mitigation for affected queries. Uninstalling the update would remove its security protections and should be weighed against the operational impact. Deployment decisions should rely on Microsoft’s advisory rather than the conflicting third-party vulnerability count and severity claims.

Patch this, or something else?See real exploitation activity before you spend the cycle.
Triage this advisory
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

2 events · Nov 10, 2026
  1. Reported Nov 10, 20268d ago

    Microsoft documents recovery-related access violations and temporary mitigations

    Microsoft documented a KB5129300 regression in which querying sys.dm_exec_requests during database recovery can trigger an access violation and generate a dump because internal structures are accessed before initialization completes. While investigating a fix, Microsoft provided temporary mitigations: enable trace flag 4696, avoid the affected queries, or uninstall the update; the trace flag can restore monitoring errors 976 or 978 on secondary replicas.

    KB5129300 - Description of the security update for SQL Server 2022 CU27: November 10, 2026 - SQL Server | Microsoft Support
  2. Nov 10, 20268d ago

    Microsoft releases SQL Server 2022 security update KB5129300

    Microsoft released KB5129300 for SQL Server 2022 CU27, updating the product to version 16.0.4315.2 and addressing 33 listed vulnerabilities: 12 remote-code-execution, 12 elevation-of-privilege, and nine information-disclosure flaws. The update strengthens memory safety, authorization, and input validation across SQL Server components and disables XSLT scripting by default in Integration Services.

    KB5129300 - Description of the security update for SQL Server 2022 CU27: November 10, 2026 - SQL Server | Microsoft Support
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.