KB5122768: SQL Server 2022 for x64-based Systems Security Update (September 2026)

Full tracking and change history for KB5122768

Released

2026-09-08

Last changed

2026-09-26

Changes tracked

5

Senserva began recording day-to-day change history on 2026-07-07, and refreshes it several times a day. Release dates are historical where Microsoft publishes them; revision history is tracked from that date forward, so it does not include changes made before then.

Check if KB5122768 is installed

Elevated PowerShell. No output means it is not installed.

Known issues, from Microsoft

Quoted from Microsoft's support article for KB5122768 (checked 2026-10-06). Verify against the article before acting.

Linked server queries that use MSDASQL fail with error 7416

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:

Msg 7416, Level 16

Access to the remote server is denied because no login-mapping exists.

A stricter connection validation check in the Database Engine can reject connections for certain linked server configurations that use the MSDASQL provider, even if earlier builds allowed those connections.

For more information and workarounds, see Linked server queries that use MSDASQL fail with error 7416 .

Access violation when you query sys.dm_exec_requests during database recovery

Queries against sys.dm_exec_requests might raise an access violation and generate a dump file if they run while a database is still recovering. This issue can occur during a database RESTORE operation, during startup recovery, or before an availability group replica finishes coming online.

The SQL Server error log contains entries that resemble the following text:

The database '<DatabaseName>' is marked RESTORING and is in a state that does not allow recovery to be run.

***Stack Dump being sent to <SQLServerLogFolder>\SQLDump0215.txt

SqlDumpExceptionHandler: Process 77 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process.

*******************************************************************************

BEGIN STACK DUMP:

07/30/26 07:37:23 spid 77

Exception Address = <frame id="00" address="0x7FFDED94970D" pdb="sqlmin.pdb" age="2" guid="E1039014-237E-4DB6-88FD-4A2AB31C651F" module="sqlmin" rva="0x2970D" />

Exception Code = c0000005 EXCEPTION_ACCESS_VIOLATION

Access Violation occurred reading address 00000000000000F0

Input Buffer <size> bytes -

<dbo.sp_YourMonitoringStoredProcedure>

This issue occurs because of a change that causes internal in-memory structures to be referenced before they're fully initialized.

Microsoft is aware of this issue and is investigating a fix. Until a fix is available, use one of the following mitigations:

Enable trace flag 4696 to opt out of the code change that causes this issue. If you enable this trace flag, monitoring queries that query sys.dm_exec_requests or sys.sysprocesses on secondary replicas might return error "976" or error "978" as they did before you installed this update.

Avoid queries against sys.dm_exec_requests for databases that are recovering.

Uninstall this update.

CVEs fixed by this update

Sorted exploited-first, then by CVSS. Every CVE links to its Senserva page with the full risk facts, references, and a ready-to-paste AI prompt.

Scope and sources

Affected products

• Microsoft SQL Server 2022 for x64-based Systems (CU 26)

Also released in September 2026

KB5122871

679 CVEs · Critical · exploited

KB5122876

616 CVEs · Critical · exploited

KB5122878

568 CVEs · Critical · exploited

KB5122880

602 CVEs · Critical · exploited

KB5122882

641 CVEs · Critical · exploited

KB5123065

393 CVEs · Critical · exploited

KB5123066

418 CVEs · Critical · exploited

KB5123099

555 CVEs · Critical · exploited

The full month, summarized: Microsoft Patch Tuesday.

Authoritative references

Official KB5122768 page (Microsoft Support)Microsoft Update CatalogMicrosoft Security Update Guide