Fixes: KB5122768: Microsoft SQL Server 2022 for x64-based Systems (CU 26) (restart required); KB5122769: Microsoft SQL Server 2025 for x64-based Systems (CU8) (restart required); KB5122770: Microsoft SQL Server 2025 for x64-based Systems (GDR) (restart required); KB5122771: Microsoft SQL Server 2022 for x64-based Systems (GDR) (restart required); KB5122772: Microsoft SQL Server 2019 for x64-based Systems (CU 32) (restart required); KB5122773: Microsoft SQL Server 2019 for x64-based Systems (GDR) (restart required); KB5122774: Microsoft SQL Server 2017 for x64-based Systems (CU 31) (restart required); KB5122775: Microsoft SQL Server 2017 for x64-based Systems (GDR) (restart required) → KB5122768: Microsoft SQL Server 2022 for x64-based Systems (CU 26) (restart required); KB5122769: Microsoft SQL Server 2025 for x64-based Systems (CU8) (restart required); KB5122770: Microsoft SQL Server 2025 for x64-based Systems (GDR) (restart required); KB5122771: Microsoft SQL Server 2022 for x64-based Systems (GDR) (restart required); KB5122772: Microsoft SQL Server 2019 for x64-based Systems (CU 32) (restart required); KB5122773: Microsoft SQL Server 2019 for x64-based Systems (GDR) (restart required); KB5122774: Microsoft SQL Server 2017 for x64-based Systems (CU 31) (restart required); KB5122775: Microsoft SQL Server 2017 for x64-based Systems (GDR) (restart required); KB5126934: Microsoft SQL Server 2022 for x64-based Systems (CU27) (restart required); KB5132745: Microsoft SQL Server 2019 for x64-based Systems (CU32) (restart required); KB5132746: Microsoft SQL Server 2017 for x64-based Systems (CU31) (restart required) · Affected products: Microsoft SQL Server 2017 for x64-based Systems (CU 31), Microsoft SQL Server 2017 for x64-based Systems (GDR), Microsoft SQL Server 2019 for x64-based Systems (CU 32), Microsoft SQL Server 2019 for x64-based Systems (GDR), Microsoft SQL Server 2022 for x64-based Systems (CU 26), Microsoft SQL Server 2022 for x64-based Systems (GDR), Microsoft SQL Server 2025 for x64-based Systems (CU8), Microsoft SQL Server 2025 for x64-based Systems (GDR) → Microsoft SQL Server 2017 for x64-based Systems (CU 31), Microsoft SQL Server 2017 for x64-based Systems (CU31), Microsoft SQL Server 2017 for x64-based Systems (GDR), Microsoft SQL Server 2019 for x64-based Systems (CU 32), Microsoft SQL Server 2019 for x64-based Systems (CU32), Microsoft SQL Server 2019 for x64-based Systems (GDR), Microsoft SQL Server 2022 for x64-based Systems (CU 26), Microsoft SQL Server 2022 for x64-based Systems (CU27), Microsoft SQL Server 2022 for x64-based Systems (GDR), Microsoft SQL Server 2025 for x64-based Systems (CU8), Microsoft SQL Server 2025 for x64-based Systems (GDR)
Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
Detection template: Unknown: detection-template evidence is incomplete or retained → No Nuclei template listed
Detection template: No Nuclei template listed → Unknown: detection-template evidence is incomplete or retained
Detection template: No Nuclei template listed · Customer action: Required: apply the update → Required: follow the MSRC remediation guidance · Public disclosure: No → No (MSRC assessment) · Exploitation detected: Not reported by MSRC → No known exploitation (MSRC assessment)
Detection template: Unknown: exploit-code evidence is incomplete or retained → No Nuclei template listed · CISA KEV: Unknown: catalog evidence is incomplete or retained → Not listed in the collected catalog
Detection template: No Nuclei template listed → Unknown: exploit-code evidence is incomplete or retained · CISA KEV: Not listed in the collected catalog → Unknown: catalog evidence is incomplete or retained
Page history
Changes are dated when recorded; day views use the last saved version from that UTC day, and citations stay fixed.
Up to 100 recent field edits are shown; older edits may be outside retention.
10 Nov 2026 · 21:34:10 UTCUpdates that fix itKB5122768: Microsoft SQL Server 2022 for x64-based Systems (CU 26) (restart required); KB5122769: Microsoft SQL Server 2025 for x64-based Systems (CU8) (restart required); KB5122770: Microsoft SQL Server 2025 for x64-based Systems (GDR) (restart required); KB5122771: Microsoft SQL Server 2022 for x64-based Systems (GDR) (restart required); KB5122772: Microsoft SQL Server 2019 for x64-based Systems (CU 32) (restart required); KB5122773: Microsoft SQL Server 2019 for x64-based Systems (GDR) (restart required); KB5122774: Microsoft SQL Server 2017 for x64-based Systems (CU 31) (restart required); KB5122775: Microsoft SQL Server 2017 for x64-based Systems (GDR) (restart required) → KB5122768: Microsoft SQL Server 2022 for x64-based Systems (CU 26) (restart required); KB5122769: Microsoft SQL Server 2025 for x64-based Systems (CU8) (restart required); KB5122770: Microsoft SQL Server 2025 for x64-based Systems (GDR) (restart required); KB5122771: Microsoft SQL Server 2022 for x64-based Systems (GDR) (restart required); KB5122772: Microsoft SQL Server 2019 for x64-based Systems (CU 32) (restart required); KB5122773: Microsoft SQL Server 2019 for x64-based Systems (GDR) (restart required); KB5122774: Microsoft SQL Server 2017 for x64-based Systems (CU 31) (restart required); KB5122775: Microsoft SQL Server 2017 for x64-based Systems (GDR) (restart required); KB5126934: Microsoft SQL Server 2022 for x64-based Systems (CU27) (restart required); KB5132745: Microsoft SQL Server 2019 for x64-based Systems (CU32) (restart required); KB5132746: Microsoft SQL Server 2017 for x64-based Systems (CU31) (restart required)
10 Nov 2026 · 21:34:10 UTCAffected productsMicrosoft SQL Server 2017 for x64-based Systems (CU 31), Microsoft SQL Server 2017 for x64-based Systems (GDR), Microsoft SQL Server 2019 for x64-based Systems (CU 32), Microsoft SQL Server 2019 for x64-based Systems (GDR), Microsoft SQL Server 2022 for x64-based Systems (CU 26), Microsoft SQL Server 2022 for x64-based Systems (GDR), Microsoft SQL Server 2025 for x64-based Systems (CU8), Microsoft SQL Server 2025 for x64-based Systems (GDR) → Microsoft SQL Server 2017 for x64-based Systems (CU 31), Microsoft SQL Server 2017 for x64-based Systems (CU31), Microsoft SQL Server 2017 for x64-based Systems (GDR), Microsoft SQL Server 2019 for x64-based Systems (CU 32), Microsoft SQL Server 2019 for x64-based Systems (CU32), Microsoft SQL Server 2019 for x64-based Systems (GDR), Microsoft SQL Server 2022 for x64-based Systems (CU 26), Microsoft SQL Server 2022 for x64-based Systems (CU27), Microsoft SQL Server 2022 for x64-based Systems (GDR), Microsoft SQL Server 2025 for x64-based Systems (CU8), Microsoft SQL Server 2025 for x64-based Systems (GDR)
CISA KEV is observed exploitation evidence. FIRST EPSS is a dated prediction of exploitation in the next 30 days. Missing scores are unknown. This collector requests predictions only for explicit CVE aliases in the public NuGet archive; Microsoft release views retain their existing prediction scope.
No collected risk observation for these identifiers. This does not establish absence of exploitation or a zero probability.
Dated risk observations
Risk history is separate from CNA/OSV content history. Daily score drift is retained but only an upward crossing of 10% triggers the prediction change event.
Immutable source observations
4 recorded revisions
Each citation identifies one complete source statement. Source modification dates and the time this installation observed them are distinct. Latest history includes records historically associated by source identifiers; a removed alias is not a current equivalence claim. Exact citations show that source record's own earlier observations. Failed reads and unchanged polls do not rewrite history.