Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege SQL Server credential
-
DeliveryConnect to SQL Server over network (TCP 1433)
-
ExploitInject malicious SQL payload into vulnerable engine path
-
ExecutionSQL Server executes payload at elevated privilege context
-
PersistAttacker gains high-privilege database access
-
ImpactRead, modify, or delete any database data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The attacker must possess a valid, low-privilege SQL Server login credential and network-level access to the SQL Server instance (typically TCP 1433 or a named-pipe equivalent). No special configuration, non-default feature, or elevated role is required beyond holding any authenticated session - the PR:L rating confirms this. Exploitation is limited by: (1) requirement for a valid database login (unauthenticated exploitation is not possible per PR:L), and (2) network reachability to the SQL Server endpoint. Environments where SQL Server is not directly network-exposed and all application accounts are tightly scoped reduce the practical attacker population but do not eliminate the vulnerability. |
| Impact | The CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects a straightforward network-reachable exploitation path requiring only a low-privilege database credential - a condition met by any application service account or developer login. The attack complexity is low, meaning no race conditions or non-default configurations are required beyond holding a valid login. The full C:H/I:H/A:H triad indicates that successful privilege escalation yields read and write access to all database data and potential availability impact. No public exploit code has been identified and the vulnerability is not listed in the CISA KEV catalog, which moderates the immediacy of mass exploitation risk. EPSS data is not provided in the input. The broad scope of affected versions - spanning four major SQL Server releases across both CU and GDR servicing tracks - means the exposure surface is large in any environment that has not yet applied July 2026 patches; even moderately sized deployments with a large authenticated user base (application accounts, reporting users, or developer access) represent meaningful risk if unpatched. |
| Exploit ScenarioDerived | An attacker with a low-privilege SQL Server login - such as a compromised application service account, a developer credential, or a shared reporting account - sends a crafted SQL query that exploits the injection flaw within SQL Server's engine to execute commands in a higher-privilege context. This does not require any special feature to be enabled or any administrative interaction. No public proof-of-concept code has been identified at time of analysis, but the low attack complexity means a working exploit would be straightforward to develop once an analyst identifies the specific injectable execution path. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 08, 2026
SQL injection in Microsoft SQL Server (versions 2017 through 2025) enables a network-authenticated low-privilege attacker to escalate privileges within the database engine. The flaw exists across all current servicing tracks - both cumulative update (CU) and general distribution release (GDR) branches - for SQL Server 2017, 2019, 2022, and 2025. No public exploit code or active exploitation has been identified at time of analysis, but vendor-released patches are available for all affected versions.
RemediationAI
Apply the vendor-released patches via Microsoft Update or manual download from the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-67370. Target fix builds are: SQL Server 2017 CU 31 → 14.0.3550.4 or later; SQL Server 2017 GDR → 14.0.2130.4 or later; SQL Server 2019 CU 32 → 15.0.4490.9 or later; SQL Server 2019 GDR → 15.0.2190.7 or later; SQL Server 2022 CU 26 → 16.0.4275.2 or later; SQL Server 2022 GDR → 16.0.1200.5 or later; SQL Server 2025 CU 8 → 17.0.4085.5 or later; SQL Server 2025 GDR → 17.0.1135.8 or later. As a compensating control where patching cannot be immediately applied, restrict database login grants to the minimum required set of users, enforce strong authentication policies to limit the pool of potential low-privilege attackers, and audit for any unexpected privilege escalation events in SQL Server logs. Note that restricting network access to the SQL Server port (default TCP 1433) to only trusted application hosts reduces the network attack surface but does not eliminate risk from already-connected legitimate users.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 8 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
CWE-89 (SQL Injection) occurs when user-supplied input is incorporated into a SQL command without adequate parameterization or escaping, allowing an attacker to alter the intended query logic. In this context, the vulnerability resides within SQL Server's own engine logic - not an application sitting atop it - meaning the injection path is internal to an authorized database session. Affected CPE ranges span SQL Server 14.x (2017) below 14.0.3550.4 (CU) and 14.0.2130.4 (GDR), SQL Server 15.x (2019) below 15.0.4490.9 (CU) and 15.0.2190.7 (GDR), SQL Server 16.x (2022) below 16.0.4275.2 (CU) and 16.0.1200.5 (GDR), and SQL Server 17.x (2025) below 17.0.4085.5 (CU) and 17.0.1135.8 (GDR). The vulnerability was reported through Microsoft's MSRC channel (secure@microsoft.com), indicating coordinated disclosure.
Know when Sql Server 2017 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Network-reachable SQL Server requires only a low-privilege login (PR:L); low complexity and no UI interaction; full C/I/A impact after privilege escalation.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
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.
Executive ViewAI
SQL Server 2017 through 2025 contains a privilege escalation vulnerability that could allow a database user with low-level access to gain elevated privileges. Organizations running any of these SQL Server versions should prioritize patching to prevent unauthorized database access and data manipulation.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Sql Server 2017
View allSQL Server 2016-2025 contains an improper access control flaw that allows authenticated network attackers to escalate pr
Heap-based buffer overflow in Microsoft SQL Server 2017, 2019, 2022, and 2025 (x64) can be triggered over the network an
Microsoft SQL Server Elevation of Privilege Vulnerability. Rated critical severity (CVSS 9.8), this vulnerability is rem
Microsoft SQL Server Elevation of Privilege Vulnerability. Rated critical severity (CVSS 9.8), this vulnerability is rem
Heap-based buffer overflow in Microsoft SQL Server 2017 and 2019 enables unauthenticated network attackers to execute ar
SQL injection in Microsoft SQL Server enables a low-privileged authenticated attacker to escalate database privileges ov
Privilege escalation in Microsoft SQL Server 2017 through 2025 allows any low-privileged authenticated database user to
Heap-based buffer overflow in Microsoft SQL Server 2017 through 2025 enables an authenticated low-privilege network atta
Remote code execution is possible in Microsoft SQL Server 2017 through 2025 via a heap-based buffer overflow (CWE-122) t
Heap-based buffer overflow in Microsoft SQL Server (versions 2017 through 2025) enables any authenticated network attack
Remote code execution in Microsoft SQL Server affects versions 2017 through 2025 via an integer overflow that triggers a
Privilege escalation in Microsoft SQL Server (versions 2017, 2019, 2022, and 2025) allows a low-privileged authenticated
EUVD-2026-73181
GHSA-9q7c-j2j7-x447
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB