Skip to main content
CVE-2025-49759VulnerabilityPublished Updated

CVE-2025-49759: Microsoft SQL Server 2016 Service Pack 3 (GDR) · SQL Injection

Affects Microsoft SQL Server 2016 Service Pack 3 (GDR)Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
1.1% chance of exploitation in 30 days – higher than 67% 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:C

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
Microsoft Microsoft SQL Server 2016 Service Pack 3 (GDR)Affected
  • =13.0.0
Fixed in–

AI-suggested

1. Apply official patches from Microsoft immediately once they become available for SQL Server 2016 SP3 (GDR). 2. Until patches are released, restrict network access to SQL Server instances to only trusted hosts and networks using firewalls and network segmentation. 3. Enforce the principle of least privilege by limiting database user permissions to the minimum necessary for their roles. 4. Implement rigorous input validation and parameterized queries in applications interacting with the database to prevent injection attacks. 5. Monitor SQL Server logs and network traffic for unusual or suspicious SQL queries that could indicate exploitation attempts. 6. Use database activity monitoring tools to detect and alert on privilege escalation or anomalous behavior. 7. Conduct regular security audits and penetration testing focused on SQL injection vulnerabilities. 8. Educate database administrators and developers about secure coding practices and the risks of SQL injection. 9. Consider upgrading to a more recent and supported version of SQL Server that may have improved security features and ongoing support.

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.

References

Community reviews

Loading reviews…