CVE-2025-59499

Microsoft SQL Server Elevation of Privilege Vulnerability

HIGH
8.8
CVSS Score
Published: November 11, 2025 at 05:59 PM UTC
Updated: June 17, 2026 at 09:46 AM UTC
4 products affected across 1 vendorSQL Server 2019SQL Server 2022SQL Server 2017

Using Microsoft SQL Server 2017 (GDR) by Microsoft?

Get instant alerts when new vulnerabilities affect Microsoft SQL Server 2017 (GDR) - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.8
Exploit prediction
EPSS 1%
SSVC
No known exploit

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

13.0.0 ≤ v < 13.0.6475.113.0.0 ≤ v < 13.0.7070.113.0.6300.2 ≤ v < 13.0.6475.113.0.7000.253 ≤ v < 13.0.7070.113.0.0
Affected range stops below 13.0.6475.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 13.0.7070.1, so it looks safe — our inference, not a vendor statement
14.0.0 ≤ v < 14.0.2095.114.0.0 ≤ v < 14.0.3515.114.0.1000.169 ≤ v < 14.0.2095.114.0.3006.16 ≤ v < 14.0.3515.114.0.0
Affected range stops below 14.0.2095.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 14.0.3515.1, so it looks safe — our inference, not a vendor statement
15.0.0 ≤ v < 15.0.2155.215.0.0.0 ≤ v < 15.0.4455.215.0.2000.5 ≤ v < 15.0.2155.215.0.4003.23 ≤ v < 15.0.4455.215.0.015.0.0.0
Affected range stops below 15.0.2155.2, so it looks safe — our inference, not a vendor statement
Affected range stops below 15.0.4455.2, so it looks safe — our inference, not a vendor statement
16.0.0 ≤ v < 16.0.1160.116.0.0.0 ≤ v < 16.0.4222.216.0.1000.6 ≤ v < 16.0.1160.116.0.4003.1 ≤ v < 16.0.4222.216.0.016.0.0.0
Affected range stops below 16.0.1160.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 16.0.4222.2, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.8HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-89

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card