DEV Community

CVE Reports
CVE Reports

Posted on • Originally published at cvereports.com

CVE-2026-47295: CVE-2026-47295: SQL Injection and Privilege Escalation in Microsoft SQL Server

#security #cve #cybersecurity

CVE-2026-47295: SQL Injection and Privilege Escalation in Microsoft SQL Server

Vulnerability ID: CVE-2026-47295
CVSS Score: 8.8
Published: 2026-07-14

CVE-2026-47295 is a high-severity elevation of privilege vulnerability in Microsoft SQL Server (2016 through 2025). An authenticated, low-privileged attacker can execute remote SQL injection commands within system stored procedures to elevate permissions to sysadmin.

TL;DR

An authenticated, low-privileged network attacker can execute SQL injection attacks against internal system stored procedures in Microsoft SQL Server, leading to full privilege escalation up to sysadmin administrative control.

Technical Details

  • CWE ID: CWE-89 (SQL Injection)
  • Attack Vector: Network (AV:N)
  • CVSS v3.1 Score: 8.8
  • EPSS Score: 0.00921 (0.92%)
  • Impact: Complete Privilege Escalation to sysadmin
  • Exploit Status: None (Theoretical)
  • CISA KEV Status: Not Listed

Affected Systems

  • Microsoft SQL Server 2016
  • Microsoft SQL Server 2017
  • Microsoft SQL Server 2019
  • Microsoft SQL Server 2022
  • Microsoft SQL Server 2025
  • SQL Server 2016 Service Pack 3: >= 13.0.0 < 13.0.6500.1 (Fixed in: 13.0.6500.1)
  • SQL Server 2017: >= 14.0.0 < 14.0.2120.1 (Fixed in: 14.0.2120.1)
  • SQL Server 2019: >= 15.0.0 < 15.0.2180.2 (Fixed in: 15.0.2180.2)
  • SQL Server 2022: >= 16.0.0 < 16.0.1190.2 (Fixed in: 16.0.1190.2)
  • SQL Server 2025: >= 17.0.0 < 17.0.1125.2 (Fixed in: 17.0.1125.2)

Mitigation Strategies

  • Apply the official GDR and Cumulative Update patches provided by Microsoft.
  • Isolate the SQL Server port interfaces behind local firewalls to prevent raw network access.
  • Revoke EXECUTE permissions from public roles on administrative system procedures.
  • Enable SQL Server Audit mechanisms to detect unauthorized role modifications.

Remediation Steps:

  1. Determine the installed edition and version level of the SQL Server database instance.
  2. Download the matching security update package from the Microsoft Update Catalog.
  3. Schedule database maintenance windows and apply the cumulative or GDR patch.
  4. Verify that the database build version matches the patched threshold.
  5. Configure Extended Events or Server Audits to monitor for administrative role promotions.

References

Read the full report for CVE-2026-47295 on our website for more details including interactive diagrams and full exploit analysis.

Top comments (0)