Microsoft SQL Server: Elevation of privilege through SQL injection
Summary
A SQL injection flaw in Microsoft SQL Server allows an authenticated attacker to elevate privileges over the network. The attacker needs a valid low-privileged database login and a high-complexity attack, and no user interaction is required. Successful exploitation can affect confidentiality, integrity and availability of the database.
Affected
- SQL Server 2017 (GDR): 14.0.0 to before 14.0.2150.2
- SQL Server 2017 for x64-based Systems (CU31): 14.0.3006.16 to before 14.0.3570.2
- SQL Server 2019 (GDR): 15.0.0 to before 15.0.2210.4
- SQL Server 2019 for x64-based Systems (CU32): 15.0.4003.23 to before 15.0.4510.2
- SQL Server 2022 (GDR): 16.0.0 to before 16.0.1220.3
- SQL Server 2022 for x64-based Systems (CU27): 16.0.4003.1 to before 16.0.4315.2
- SQL Server 2025 CU10: 17.0.4006.0 to before 17.0.5045.3
- SQL Server 2025 for x64-based Systems (GDR): 17.0.1050.2 to before 17.0.1155.3
- Other branches: Unknown. Verify on the MSRC page.
Fixed in
- SQL Server 2017 (GDR): 14.0.2150.2
- SQL Server 2017 for x64-based Systems (CU31): 14.0.3570.2
- SQL Server 2019 (GDR): 15.0.2210.4
- SQL Server 2019 for x64-based Systems (CU32): 15.0.4510.2
- SQL Server 2022 (GDR): 16.0.1220.3
- SQL Server 2022 for x64-based Systems (CU27): 16.0.4315.2
- SQL Server 2025 CU10: 17.0.5045.3
- SQL Server 2025 for x64-based Systems (GDR): 17.0.1155.3
Workaround
No vendor workaround found. Patching is the only documented remedy.
Exploitation
- CISA SSVC: exploitation none, not automatable, technical impact total
- Rapid7 (November 2026): exploitation less likely, not publicly disclosed
- No confirmed exploitation and no public proof of concept found
- Not listed in CISA KEV (not found in sources)
Our recommendation
- Patch all affected SQL Server instances in the November 2026 cycle, using the build listed for each branch.
- Verify exact builds against the Microsoft Security Update Guide before rollout.
- Patch the other SQL Server elevation-of-privilege CVEs in the same update (CVE-2026-118110, CVE-2026-118113, CVE-2026-118116) at the same time.
- Restrict network access to SQL Server and do not expose it to the internet.
- Limit database logins to least privilege and review accounts with valid access.
- Check which SQL Server instances are exposed and monitor database logs for unusual activity.
Information from Microsoft (Patch Tuesday November 2026)
Public exploits
PoC-in-GitHub, Metasploit and Exploit-DB list nothing for this CVE.
Research sources
- Microsoft Security Update Guide: CVE-2026-118114 msrc.microsoft.com
- CVE Record: CVE-2026-118114 www.cve.org
- Microsoft KB5132748 (SQL Server 2025 GDR, November 2026) support.microsoft.com
- Rapid7: Patch Tuesday November 2026 www.rapid7.com
- threatint: CVE-2026-118114 cve.threatint.com
Researched and written up in English and German by an AI (Claude by Anthropic) based on NVD, CISA, EPSS and the sources listed. The vendor information is authoritative. Researched on 11 Nov 2026, 05:38.
Original description (NVD)
Improper neutralization of special elements used in an sql command ('sql injection') in SQL Server allows an authorized attacker to elevate privileges over a network.
NVD references (1)
Sources
The tracker combines official, freely usable data sources – updated continuously:
- NVD (NIST) – CVEs, rating (CVSS), affected products
- CISA KEV – vulnerabilities confirmed by CISA as actively exploited
- CISA Vulnrichment – CISA assessment (SSVC) in the official CVE record
- FIRST EPSS – probability of exploitation
- Microsoft MSRC – Patch Tuesday: vulnerabilities, severity, updates
- PoC-in-GitHub – public proof-of-concept repositories
- Metasploit (Rapid7) – modules of the Metasploit Framework
- Exploit-DB (OffSec) – archive of public exploits (links only)
- Patch days: official vendor pages (linked per vendor) (Vendor patch days)
This product uses data from the NVD API but is not endorsed or certified by the NVD. EPSS data © FIRST.org.
Affected? We can help.
We check whether your systems are affected, install updates and close the gap – continuously with the System Health Checker if you wish.