Skip to main content
CVE-2025-24999VulnerabilityPublished Updated

CVE-2025-24999: Microsoft SQL Server 2016 Service Pack 3 (GDR) · Improper Access Control

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, 08:30 UTC

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

Until official patches are released, organizations should implement the following specific mitigations: 1) Restrict network access to SQL Server instances by limiting inbound connections to trusted hosts and networks using firewalls and network segmentation. 2) Enforce the principle of least privilege by auditing and minimizing user privileges on SQL Server, ensuring no unnecessary elevated rights are granted. 3) Monitor SQL Server logs and network traffic for unusual privilege escalation attempts or anomalous behavior indicative of exploitation attempts. 4) Apply strict authentication and authorization policies, including multi-factor authentication for administrative accounts where possible. 5) Disable or restrict features and services in SQL Server that are not required, reducing the attack surface. 6) Prepare for rapid deployment of patches once Microsoft releases updates by maintaining an up-to-date asset inventory and patch management process. 7) Consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect exploitation patterns related to privilege escalation in SQL Server environments.

Description

Improper access control in SQL Server allows an authorized attacker to elevate privileges over a network.

References

Community reviews

Loading reviews…