Patch tracker / KB5126934
KB5126934: SQL Server 2022 Security Update (October 2026)
KB5126934 is a High security update for SQL Server 2022, released 2026-10-13. It closes 18 CVEs with a maximum CVSS of 8.8. Microsoft documents 1 known issue for this update, quoted below.
Before you deploy: Microsoft lists 1 known issue for this update.
Our data comes from Microsoft, CISA and other public sources, and it can be wrong or out of date. If you are unsure, check the linked source before you act, and tell us when we are wrong so we can fix it.
Update summary
Fixes 18 CVEs. Most severe CVSS 8.8 (High). EPSS exploit probability up to 1.6%. Among the lower half of tracked Microsoft updates by EPSS exploit probability.
A newer security update for Microsoft SQL Server 2022 for x64-based Systems (CU27) has shipped since this one: KB5129300 (2026-11-10). For cumulative update families the newer package includes these fixes, so installing that one is usually the shorter path. Verify against your own update rings before you skip this package.
Microsoft documents 1 known issue with this update.
- Linked server queries that use MSDASQL fail with error 7416
Senserva AI Opinion and rich prompt for KB5126934
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5126934
- Released
- 2026-10-13
- Last changed
- 2026-11-10
- 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 KB5126934 is installed
This update is for Microsoft SQL Server 2022 for x64-based Systems, not a Windows component, so Get-HotFix does not list it. Compare the installed version of the product with the build Microsoft lists for this update.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5126934 (checked 2026-11-10). Microsoft lists 1 known issue. 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.
| CVE | Severity | CVSS | EPSS | Exploited |
|---|---|---|---|---|
| CVE-2026-65674 | High | 8.8 | 1.6% | No |
| CVE-2026-67625 | High | 8.5 | <1% | No |
| CVE-2026-68883 | High | 8.5 | <1% | No |
| CVE-2026-85886 | High | 8.5 | <1% | No |
| CVE-2026-85888 | High | 7.7 | <1% | No |
| CVE-2026-88081 | High | 7.7 | <1% | No |
| CVE-2026-88083 | High | 7.5 | <1% | No |
| CVE-2026-85876 | High | 7.0 | <1% | No |
| CVE-2026-85919 | High | 7.0 | <1% | No |
| CVE-2026-88082 | High | 7.0 | <1% | No |
| CVE-2026-88088 | High | 7.0 | <1% | No |
| CVE-2026-32176 | Medium | 6.7 | <1% | No |
| CVE-2026-70189 | Medium | 6.7 | <1% | No |
| CVE-2026-67626 | Medium | 6.5 | <1% | No |
| CVE-2026-67645 | Medium | 6.5 | <1% | No |
| CVE-2026-88085 | Medium | 6.4 | <1% | No |
| CVE-2026-88086 | Medium | 5.3 | <1% | No |
| CVE-2026-67628 | Medium | 4.9 | <1% | No |
Scope and sources
- Affected products
- Also released in October 2026
KB5126646
1097 CVEs · Critical · exploitedKB5126651
973 CVEs · Critical · exploitedKB5126653
1021 CVEs · Critical · exploitedKB5126655
1033 CVEs · Critical · exploitedKB5126657
954 CVEs · Critical · exploitedKB5126836
666 CVEs · Critical · exploitedKB5126868
785 CVEs · Critical · exploitedKB5127646
1055 CVEs · Critical · exploitedThe full month, summarized: Microsoft Patch Tuesday.
- Authoritative references
See this and every Microsoft update ranked by real-world risk on the Microsoft Patch Tracker.