CVE-2026-88085: Microsoft SQL Server Elevation of Privilege Vulnerability
Heap-based buffer overflow in SQL Server allows an authorized attacker to elevate privileges locally.
Other sources
Microsoft SQL Server Elevation of Privilege Vulnerability
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 14.0.2140.2Patch KB5128497 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 17.0.5015.4Patch KB5126967 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 15.0.4500.2Patch KB5128494 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.0.1210.3Patch KB5128493 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 16.0.4305.5Patch KB5126934 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 14.0.3560.2Patch KB5128496 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 17.0.1145.4Patch KB5128492 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 15.0.2200.2Patch KB5128495
Event History
Frequently Asked Questions
Who can exploit this vulnerability?
An attacker must already be authorized on the affected SQL Server system and able to perform local actions. The available data does not indicate that it is exploitable remotely or without authentication.
What is the likely impact if exploitation succeeds?
Successful exploitation allows local elevation of privilege. The supplied severity vector indicates potential high impact to confidentiality, integrity, and availability.
Which SQL Server releases should be reviewed?
Review deployments of Microsoft SQL Server 2017, 2019, 2022, and 2025, including the listed 2017 CU31, 2019 CU32, 2022 CU27, and 2025 CU9 entries. The data does not state whether other cumulative update levels are affected or fixed.
What can be done if patching cannot happen immediately?
Limit authorized local access to affected SQL Server hosts and review which accounts can execute or administer software on those systems. This reduces exposure because exploitation requires an authorized attacker with local access.