Microsoft SQL Server 2016 Service Pack 3 (GDR): Improper Privilege Management
CVE-2025-49758 is a high-severity improper privilege management vulnerability in Microsoft SQL Server 2016 Service Pack 3 (GDR) from Microsoft, with a CVSS 3.1 base score of 8.8 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists version 13.0.6465.1 as the first without the flaw, so updating Microsoft SQL Server 2016 Service Pack 3 (GDR) to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.07% chance of exploitation within 30 days, higher than 65% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Microsoft SQL Server 2016 Service Pack 3 (GDR) to 13.0.6465.1 or a later version.
- Update Microsoft SQL Server 2016 Service Pack 3 Azure Connect Feature Pack to 13.0.7060.1 or a later version.
- Update Microsoft SQL Server 2017 (CU 31) to 14.0.3500.1 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 2016 Service Pack 3 (GDR) | 13.0.0 up to, but not including, 13.0.6465.1 | 13.0.6465.1 |
| Microsoft | Microsoft SQL Server 2016 Service Pack 3 Azure Connect Feature Pack | 13.0.0 up to, but not including, 13.0.7060.1 | 13.0.7060.1 |
| Microsoft | Microsoft SQL Server 2017 (CU 31) | 14.0.0 up to, but not including, 14.0.3500.1 | 14.0.3500.1 |
| Microsoft | Microsoft SQL Server 2017 (GDR) | 14.0.0 up to, but not including, 14.0.2080.1 | 14.0.2080.1 |
| Microsoft | Microsoft SQL Server 2019 (CU 32) | 15.0.0.0 up to, but not including, 15.0.4440.1 | 15.0.4440.1 |
| Microsoft | Microsoft SQL Server 2019 (GDR) | 15.0.0 up to, but not including, 15.0.2140.1 | 15.0.2140.1 |
| Microsoft | Microsoft SQL Server 2022 (CU 20) | 16.0.0.0 up to, but not including, 16.0.4210.1 | 16.0.4210.1 |
| Microsoft | Microsoft SQL Server 2022 (GDR) | 16.0.0 up to, but not including, 16.0.1145.1 | 16.0.1145.1 |
| Microsoft | SQL Server 2016 | 13.0.6300.2 up to, but not including, 13.0.6465.1; 13.0.7000.253 up to, but not including, 13.0.7060.1 | 13.0.6465.1, 13.0.7060.1 |
| Microsoft | SQL Server 2017 | 14.0.1000.169 up to, but not including, 14.0.2080.1; 14.0.3006.16 up to, but not including, 14.0.3500.1 | 14.0.2080.1, 14.0.3500.1 |
| Microsoft | SQL Server 2019 | 15.0.2000.5 up to, but not including, 15.0.2140.1; 15.0.4003.23 up to, but not including, 15.0.4440.1 | 15.0.2140.1, 15.0.4440.1 |
| Microsoft | SQL Server 2022 | 16.0.1000.6 up to, but not including, 16.0.1145.1; 16.0.4003.1 up to, but not including, 16.0.4210.1 | 16.0.1145.1, 16.0.4210.1 |
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
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- 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:N/AC:L/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 over a network.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Privilege Management
The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Follow the principle of least privilege when assigning access rights to entities in a software system.
- Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.
More Improper Privilege Management vulnerabilities (CWE-269)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Microsoft SQL Server 2016 Service Pack 3 (GDR)
- 8.8 High severity
- 7.5 High severity
- 7.8 High severity
- 7.8 High severity
- 8.8 High severity
- 8.8 High severity
Recent Improper Privilege Management vulnerabilities
- 7.2 High severity
- 7.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 8.0 High severity
- 7.8 High severity
Spotted an error? Tell us.