CVE-2026-66814

8.8

Microsoft · SQL Server

A privilege escalation vulnerability exists in Microsoft SQL Server due to insufficient access control granularity, allowing authenticated attackers to elevate their privileges over a network.

Executive summary

A privilege escalation vulnerability in Microsoft SQL Server allows an authenticated attacker to compromise the integrity and availability of the database system.

Vulnerability

This vulnerability, categorized as CWE-1220, involves insufficient granularity of access control within the SQL Server engine. An attacker who has already obtained low-level authenticated access can exploit this flaw to perform unauthorized actions with elevated privileges.

Business impact

The vulnerability carries a CVSS score of 8.8, indicating a high level of risk. Successful exploitation allows an attacker to achieve full administrative control over the database, leading to potential data exfiltration, unauthorized modification of sensitive records, or total service disruption.

Remediation

Immediate Action: Administrators must update Microsoft SQL Server instances to the respective fixed versions: 14.0.3550.4 (2017 CU 31), 14.0.2130.4 (2017 GDR), 15.0.4490.9 (2019 CU 32), 15.0.2190.7 (2019 GDR), 16.0.4275.2 (2022 CU 26), or 16.0.1200.5 (2022 GDR).

Proactive Monitoring: Review SQL Server audit logs for unusual privilege escalation events or unexpected execution of administrative stored procedures by standard users.

Compensating Controls: Ensure that the principle of least privilege is strictly enforced for all database user accounts to limit the blast radius of any account compromise.

Exploitation status

Public Exploit Available: No

Analyst recommendation

Given the high CVSS score and the potential for full privilege escalation, this vulnerability presents a significant risk to enterprise data integrity. Security teams should prioritize patching all affected SQL Server instances across the network to prevent unauthorized administrative access.

More Microsoft CVEs all →

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources