Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate with low-privilege SQL credentials
-
ExploitSend crafted resource-intensive request
-
ExecutionTrigger uncontrolled resource consumption
-
ImpactExhaust CPU/memory, deny service
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires valid low-privilege authenticated access (PR:L) to a network-reachable Microsoft SQL Server instance - the attacker must be able to log in and submit requests/queries to the database engine. No user interaction is needed (UI:N) and attack complexity is low (AC:L). Affected builds are Microsoft SQL Server 2022 (CU27 before 16.0.4305.5; GDR before 16.0.1210.3) and SQL Server 2025 (CU9 before 17.0.5015.4; GDR before 17.0.1145.4). The authentication requirement is the primary limiting factor: instances not exposed to untrusted or low-trust accounts (e.g., single-tenant, network-segmented back-end databases) face substantially reduced risk, while hosted, shared, or internet-facing instances with broad login access are more exposed. Impact is confined to availability (service denial); no confidentiality or integrity impact applies. |
| Impact | This is a moderate, not critical, priority. The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H, base 6.5) describes a network-reachable, low-complexity resource-exhaustion flaw (CWE-400) that requires low-privilege authentication (PR:L) and impacts availability only (C:N/I:N - no data compromise). Multiple exploitation signals align toward LOW real-world urgency: CISA's SSVC decision framework reports Exploitation=none, Automatable=no, and Technical Impact=partial, and there is no CISA KEV listing and no public proof-of-concept. No EPSS score was provided in the input, so probabilistic exploitation likelihood cannot be quantified - this is a data gap, not a low score. The requirement for valid (low-privilege) credentials materially constrains the attacker population to users who can already authenticate to the SQL Server instance, meaning this is far more relevant to multi-tenant, hosted, or internet-exposed database environments than to well-segmented internal deployments. Bottom line: a genuine but bounded availability risk - worth patching on a normal cadence rather than an emergency one, absent evidence of exploitation. |
| Exploit ScenarioDerived | An attacker who already possesses low-privilege credentials to a reachable SQL Server instance submits specially crafted queries or requests that trigger uncontrolled resource consumption (CPU, memory, or similar), degrading or denying service to legitimate users. No proof-of-concept or active exploitation has been identified, and the low attack complexity (AC:L) means a knowledgeable authenticated user could trigger it reliably without special timing or race conditions. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Denial of service in Microsoft SQL Server 2022 and SQL Server 2025 allows an authenticated attacker with only low-privilege login rights to exhaust server resources over a network connection, rendering the database engine unresponsive to legitimate queries. The flaw is rated CVSS 6.5 (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H), so impact is confined to availability with no confidentiality or integrity exposure, and CISA's SSVC assessment rates exploitation as none, automation as not automatable, and technical impact as partial. No public exploit code has been identified at time of analysis and the issue is not in CISA KEV; a vendor patch is available, making this a moderate-priority hardening item rather than an emergency.
RemediationAI
Apply the Microsoft vendor patch; per the vendor advisory (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-67626), the fixed builds are SQL Server 2022 CU27 at 16.0.4305.5, SQL Server 2022 GDR at 16.0.1210.3, SQL Server 2025 CU9 at 17.0.5015.4, and SQL Server 2025 GDR at 17.0.1145.4 - install the update matching whichever servicing branch (CU or GDR) each instance currently follows, and note that patch availability is listed as 'Available from vendor' in the source data. Until maintenance windows allow patching, apply compensating controls targeted at the authentication prerequisite: audit and prune SQL logins and Windows-authenticated principals that do not need access, revoking CONNECT and unnecessary query permissions so the low-privilege accounts required by the vector (PR:L) are as few as possible - this reduces exposure but does not fix the underlying flaw and may break application service accounts if over-restricted. Use Resource Governor to cap CPU, memory, and request concurrency for untrusted or shared workload groups, accepting that aggressive caps can throttle legitimate batch and reporting workloads. Where the instance does not need to serve low-trust clients, restrict network reachability to trusted application subnets or private endpoints via firewall rules and disable unused protocols, trading accessibility for a materially smaller attack surface. Monitor for repeated connection storms, rising worker-thread or memory pressure, and abnormal query patterns as an early indicator, though detection is unlikely to be automatic given the SSVC 'not automatable' rating.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 4 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause falls under CWE-400, Uncontrolled Resource Consumption, meaning the SQL Server engine fails to bound the resources one or more operations can claim - the classic pattern behind memory, worker-thread, connection-slot, or tempdb exhaustion triggered by crafted but syntactically valid requests. The CVSS vector places the attack strictly over the network (AV:N) with low complexity (AC:L) and no user interaction (UI:N), but requires a valid low-privilege account (PR:L), so the vulnerable surface is the query/request-handling layer reachable by any authenticated login rather than a pre-authentication parser bug. Scope is unchanged (S:U), confirming the resource pressure stays within the SQL Server instance and does not pivot to the host or other components, and the only degraded security property is availability (A:H with C:N/I:N). Because exploitation requires an existing login, the practical risk profile is governed far more by who can reach and authenticate to the instance than by the raw CVSS number.
Know when the next one hits your stack
- 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:N/I:N/A:H
Network-reachable (AV:N) and low-complexity (AC:L) but requires an authenticated low-privilege login (PR:L); availability-only impact (A:H) with no confidentiality or integrity effect.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Uncontrolled resource consumption in SQL Server allows an authorized attacker to deny service over a network.
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
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
EUVD-2026-100606
GHSA-w7cx-4jpr-vh3m
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB