Skip to main content
VulnerabilityPublished Updated

CVE-2025-55227: Microsoft SQL Server 2016 Service Pack 3 (GDR) · Command 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, 17:16 UTC

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

To mitigate CVE-2025-55227, organizations should: 1) Monitor Microsoft’s official channels closely for patches or security updates addressing this vulnerability and apply them promptly once available. 2) Restrict network access to SQL Server instances by implementing strict firewall rules and network segmentation to limit exposure only to trusted hosts and administrators. 3) Enforce the principle of least privilege by reviewing and minimizing SQL Server user permissions, ensuring that users and service accounts have only necessary rights. 4) Enable and monitor detailed SQL Server logging and auditing to detect unusual command executions or privilege escalations. 5) Deploy intrusion detection and prevention systems (IDS/IPS) with signatures or heuristics capable of identifying command injection attempts targeting SQL Server. 6) Conduct regular security assessments and penetration testing focused on SQL Server environments to identify potential exploitation paths. 7) Educate administrators and security teams about this vulnerability and the importance of rapid response to suspicious activities. These steps go beyond generic advice by emphasizing proactive network controls, privilege management, and monitoring tailored to SQL Server environments.

Description

Improper neutralization of special elements used in a command ('command injection') in SQL Server allows an authorized attacker to elevate privileges over a network.

References

Community reviews

Loading reviews…