CVE-2025-49758: Microsoft SQL Server 2016 Service Pack 3 (GDR) · Improper Privilege Management
Affects Microsoft SQL Server 2016 Service Pack 3 (GDR)Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 08:30 UTC
- EPSS
- 0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:CExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Microsoft SQL Server 2016 Service Pack 3 (GDR) | Affected
| Fixed in– |
AI-suggested
1. Monitor Microsoft security advisories closely and apply official patches or updates for SQL Server 2016 SP3 as soon as they are released. 2. Until patches are available, restrict network access to SQL Server instances using firewalls and network segmentation, limiting connections to trusted hosts only. 3. Implement strict input validation and parameterized queries in all applications interacting with SQL Server to reduce the risk of SQL injection. 4. Review and enforce the principle of least privilege for all SQL Server accounts, ensuring users have only the minimum necessary permissions. 5. Enable and monitor detailed SQL Server audit logs to detect unusual or unauthorized activities indicative of exploitation attempts. 6. Conduct regular vulnerability assessments and penetration testing focused on SQL injection and privilege escalation vectors. 7. Educate database administrators and developers about secure coding practices and the risks associated with improper privilege management. 8. Consider upgrading to a more recent, supported version of SQL Server if feasible, as newer versions may have improved security controls.
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.