Microsoft SQL Server 2017 (GDR): Improper Neutralization of Special Elements used in an SQL Command
CVE-2026-118116 is a high-severity improper neutralization of special elements used in an SQL command vulnerability in Microsoft SQL Server 2017 (GDR) from Microsoft, with a CVSS 3.1 base score of 7.0 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 14.0.2150.2 as the first without the flaw, so updating Microsoft SQL Server 2017 (GDR) to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.94% chance of exploitation within 30 days, higher than 80% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Microsoft SQL Server 2017 (GDR) to 14.0.2150.2 or a later version.
- Update Microsoft SQL Server 2017 for x64-based Systems (CU31) to 14.0.3570.2 or a later version.
- Update Microsoft SQL Server 2019 (GDR) to 15.0.2210.4 or a later version.
- Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Microsoft SQL Server 2017 (GDR) | 14.0.0 up to, but not including, 14.0.2150.2 | 14.0.2150.2 |
| Microsoft | Microsoft SQL Server 2017 for x64-based Systems (CU31) | 14.0.3006.16 up to, but not including, 14.0.3570.2 | 14.0.3570.2 |
| Microsoft | Microsoft SQL Server 2019 (GDR) | 15.0.0 up to, but not including, 15.0.2210.4 | 15.0.2210.4 |
| Microsoft | Microsoft SQL Server 2019 for x64-based Systems (CU32) | 15.0.4003.23 up to, but not including, 15.0.4510.2 | 15.0.4510.2 |
| Microsoft | Microsoft SQL Server 2022 (GDR) | 16.0.0 up to, but not including, 16.0.1220.3 | 16.0.1220.3 |
| Microsoft | Microsoft SQL Server 2022 for x64-based Systems (CU27) | 16.0.4003.1 up to, but not including, 16.0.4315.2 | 16.0.4315.2 |
| Microsoft | Microsoft SQL Server 2025 CU10 | 17.0.4006.0 up to, but not including, 17.0.5045.3 | 17.0.5045.3 |
| Microsoft | Microsoft SQL Server 2025 for x64-based Systems (GDR) | 17.0.1050.2 up to, but not including, 17.0.1155.3 | 17.0.1155.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).
Official description
Improper neutralization of special elements used in an sql command ('sql injection') in SQL Server allows an authorized attacker to elevate privileges locally.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Neutralization of Special Elements used in an SQL Command
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
How developers prevent this class of flaw
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using persistence layers such as Hibernate or Enterprise Java Beans, which can provide significant protection against SQL injection if used properly.
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.
More Improper Neutralization of Special Elements used in an SQL Command vulnerabilities (CWE-89)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
References
Other vulnerabilities in Microsoft SQL Server 2017 (GDR)
- 8.8 High severity
- 8.0 High severity
- 8.0 High severity
- 8.0 High severity
- 7.5 High severity
- 7.5 High severity
Recent Improper Neutralization of Special Elements used in an SQL Command vulnerabilities
- 9.9 Critical severity
- 9.4 Critical severity
- 8.3 High severity
- 9.9 Critical severity
- 9.9 Critical severity
- 9.9 Critical severity
Spotted an error? Tell us.