Patch tracker / KB5122769
KB5122769: Microsoft SQL Server 2019 for x64-base Security Update (September 2026)
KB5122769 is a High security update for Microsoft SQL Server 2019 for x64-base, released 2026-09-08. It closes 56 CVEs with a maximum CVSS of 8.8. It is the 11th largest of the 60 updates Microsoft shipped that month, by CVEs closed.
Update summary
Fixes 56 CVEs. Most severe CVSS 8.8 (High). EPSS exploit probability up to 1.1%. Among the lower half of tracked Microsoft updates by EPSS exploit probability.
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 KB5122769
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for KB5122769
- Released
- 2026-09-08
- Last changed
- 2026-09-10
- Changes tracked
- 2
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 KB5122769 is installed
Elevated PowerShell. No output means it is not installed.
Known issues, from Microsoft
Quoted from Microsoft's support article for KB5122769 (checked 2026-09-09). 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. ...
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-66814 | High | 8.8 | 1.1% | No |
| CVE-2026-66818 | High | 8.8 | 1.1% | No |
| CVE-2026-66819 | High | 8.8 | 1.1% | No |
| CVE-2026-66820 | High | 8.8 | 1.1% | No |
| CVE-2026-67368 | High | 8.8 | 1.1% | No |
| CVE-2026-67370 | High | 8.8 | 1.1% | No |
| CVE-2026-67373 | High | 8.8 | 1.1% | No |
| CVE-2026-67380 | High | 8.8 | 1.1% | No |
| CVE-2026-67381 | High | 8.8 | 1.1% | No |
| CVE-2026-67384 | High | 8.8 | 1.1% | No |
| CVE-2026-67385 | High | 8.8 | 1.1% | No |
| CVE-2026-67388 | High | 8.8 | 1.1% | No |
| CVE-2026-67631 | High | 8.8 | 1.1% | No |
| CVE-2026-67638 | High | 8.8 | 1.1% | No |
| CVE-2026-67639 | High | 8.8 | 1.1% | No |
| CVE-2026-67642 | High | 8.8 | 1.1% | No |
| CVE-2026-67643 | High | 8.8 | 1.1% | No |
| CVE-2026-68775 | High | 8.8 | 1.1% | No |
| CVE-2026-68785 | High | 8.8 | 1.1% | No |
| CVE-2026-68786 | High | 8.8 | 1.1% | No |
| CVE-2026-73028 | High | 8.8 | 1.1% | No |
| CVE-2026-77480 | High | 8.8 | 1.1% | No |
| CVE-2026-77481 | High | 8.8 | 1.1% | No |
| CVE-2026-77483 | High | 8.8 | 1.1% | No |
| CVE-2026-77484 | High | 8.8 | 1.1% | No |
| CVE-2026-77487 | High | 8.8 | 1.1% | No |
| CVE-2026-67378 | High | 8.5 | 1.1% | No |
| CVE-2026-67379 | High | 8.5 | 1.1% | No |
| CVE-2026-67636 | High | 8.5 | 1.1% | No |
| CVE-2026-47297 | High | 8.1 | 1.2% | No |
| CVE-2026-68787 | High | 7.8 | 1.1% | No |
| CVE-2026-67376 | High | 7.5 | 1.1% | No |
| CVE-2026-77485 | High | 7.0 | 1.1% | No |
| CVE-2026-66816 | Medium | 6.5 | 1.1% | No |
| CVE-2026-67369 | Medium | 6.5 | 1.1% | No |
| CVE-2026-67383 | Medium | 6.5 | 1.1% | No |
| CVE-2026-67386 | Medium | 6.5 | 1.1% | No |
| CVE-2026-67389 | Medium | 6.5 | 1.1% | No |
| CVE-2026-67390 | Medium | 6.5 | 1.1% | No |
| CVE-2026-67393 | Medium | 6.5 | 1.1% | No |
| CVE-2026-67624 | Medium | 6.5 | 1.1% | No |
| CVE-2026-67629 | Medium | 6.5 | 1.1% | No |
| CVE-2026-67630 | Medium | 6.5 | 1.1% | No |
| CVE-2026-67633 | Medium | 6.5 | 1.1% | No |
| CVE-2026-67641 | Medium | 6.5 | 1.1% | No |
| CVE-2026-67645 | Medium | 6.5 | 1.1% | No |
| CVE-2026-67648 | Medium | 6.5 | 1.1% | No |
| CVE-2026-68776 | Medium | 6.5 | 1.1% | No |
| CVE-2026-68777 | Medium | 6.5 | 1.1% | No |
| CVE-2026-68778 | Medium | 6.5 | 1.1% | No |
| CVE-2026-68779 | Medium | 6.5 | 1.1% | No |
| CVE-2026-68780 | Medium | 6.5 | 1.1% | No |
| CVE-2026-68781 | Medium | 6.5 | 1.1% | No |
| CVE-2026-68784 | Medium | 6.5 | 1.1% | No |
| CVE-2026-73029 | Medium | 6.5 | 1.1% | No |
| CVE-2026-77488 | Medium | 5.5 | 1.1% | No |
Scope and sources
- Affected products
- Also released in September 2026
KB5122871
679 CVEs · Critical · exploitedKB5122876
616 CVEs · Critical · exploitedKB5122878
568 CVEs · Critical · exploitedKB5122880
602 CVEs · Critical · exploitedKB5122882
641 CVEs · Critical · exploitedKB5123065
393 CVEs · Critical · exploitedKB5123066
418 CVEs · Critical · exploitedKB5123099
555 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.