Skip to main content
VulnerabilityPublished Updated

CVE-2025-59499: 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 26 Oct 2026, 14:05 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 11 Nov 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 26 Oct 2026.

What to do

Affected software

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

AI-suggested

Organizations should immediately assess their exposure to Microsoft SQL Server 2016 Service Pack 3 (GDR) version 13.0.0 and prioritize remediation. Although no official patches are available at disclosure, organizations should monitor Microsoft’s security advisories for updates and apply patches promptly once released. In the interim, implement strict input validation and parameterized queries to prevent SQL injection attacks. Employ network segmentation and restrict SQL Server access to trusted hosts and networks only. Enable and review detailed logging and monitoring to detect suspicious SQL activity indicative of injection attempts. Limit privileges of SQL Server accounts to the minimum necessary to reduce the potential impact of privilege escalation. Consider deploying Web Application Firewalls (WAFs) or database activity monitoring tools that can detect and block SQL injection patterns. Regularly conduct security assessments and penetration testing focused on SQL injection vulnerabilities to identify and remediate weaknesses proactively.

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…