Skip to main content

Microsoft SQL Server EUVDEUVD-2026-73316

| CVE-2026-67636 CRITICAL
Out-of-bounds Read (CWE-125)
2026-09-08 secure@microsoft.com GHSA-9r6v-wqq6-8v3r
9.0
CVSS 3.1 · NVD
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain network access to SQL Server
  2. Delivery
    Authenticate / submit crafted query input
  3. Exploit
    Trigger out-of-bounds read in parser
  4. Execution
    Leverage read into code execution
  5. Impact
    Compromise database server and adjacent scope

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK

1 technique across 1 tactic: Collection

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation targets Microsoft SQL Server 2019 (builds before 15.0.2190.7 GDR / 15.0.4490.9 CU32), SQL Server 2022 (before 16.0.1200.5 GDR / 16.0.4275.2 CU26), and SQL Server 2025 (before 17.0.1135.8 GDR / 17.0.4085.5 CU8) on x64. The CVSS vector states PR:N/UI:N (no authentication, no user interaction), but the description's phrase 'authorized attacker' indicates a valid database connection/low-privilege account is realistically required - a meaningful limiting factor since SQL Server is typically not internet-exposed. High attack complexity (AC:H) further limits reliable exploitation, as the OOB read must be steered into code execution under specific memory conditions. Realistic exposure is highest where SQL Server accepts connections from untrusted or semi-trusted network segments.

Impact

This is a high-CVSS (9.0) SQL Server flaw where a code-quality bug (CWE-125 out-of-bounds read) is claimed by Microsoft to enable remote code execution with total technical impact (C:H/I:H/A:H, S:C). However, multiple signals argue against treating it as an immediate emergency. The CVSS vector carries AC:H, meaning exploitation is not straightforward and likely requires specific memory-layout conditions or timing. EPSS is low at 0.47% (40th percentile), and CISA's SSVC framework rates Exploitation as 'none' and Automatable as 'no' - consistent with no public exploit identified at time of analysis. A patch is already available from Microsoft. There is a notable internal conflict: the CVSS vector states PR:N (unauthenticated) while the description says 'authorized attacker,' which implies some authenticated access is actually required; Microsoft's Update Guide routinely encodes 'authorized attacker' scenarios yet publishes PR:N, so the true prerequisite is very likely low-privilege authentication rather than fully anonymous access - verify with the MSRC advisory. Net: a genuinely serious flaw worth prompt patching in exposed SQL Server estates, but the combination of AC:H, low EPSS, no known exploitation, and 'automatable: no' places it below internet-facing, PR:N/AC:L RCEs in triage priority.

Exploit ScenarioDerived

An attacker with the ability to authenticate to or submit crafted input to an affected SQL Server 2019/2022/2025 instance sends specially crafted data that triggers an out-of-bounds read in a parsing/processing path. By controlling adjacent memory, the attacker leverages the read primitive into code execution in the SQL Server process context, with the CVSS scope change (S:C) implying impact beyond the immediate component. No public exploit code has been identified at time of analysis, and the high attack complexity (AC:H) suggests non-trivial exploitation.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.5% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv2 – Sep 17, 2026

Out-of-bounds read in Microsoft SQL Server 2019, 2022, and 2025 on x64 can, under specific memory conditions, be steered into remote code execution against the database engine. The vendor scores this 9.0 (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H), while our assessment rates it 9.0 under a more conservative vector (AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) because the advisory's own 'authorized attacker' wording and Microsoft's history with SQL Server flaws indicate a valid database login is realistically required; high attack complexity (AC:H) further limits reliable exploitation to environments where SQL Server accepts connections from untrusted or semi-trusted network segments. There is no indication of active exploitation (not in CISA KEV; SSVC exploitation 'none'), no public exploit code identified at time of analysis, and EPSS is low at 0.47% (40th percentile), making this a patch-priority issue for exposed or multi-tenant SQL Server deployments rather than an emergency internet-wide threat; vendor-released patches are available.

Earlier versions of this analysis (1)
v1 Sep 08, 2026 - 21:41 CVSS 8.5

Out-of-bounds read in Microsoft SQL Server 2019, 2022, and 2025 enables an authenticated low-privilege attacker to execute arbitrary code over the network with scope-changed impact. The CWE-125 memory safety flaw in the database engine is reachable via standard SQL Server network access, and the scope-changed CVSS vector (S:C) indicates successful exploitation can escape the SQL Server process boundary to affect the underlying host. No public exploit code and no CISA KEV listing are confirmed at time of analysis; the AC:H metric signals non-trivial exploitation complexity, but the breadth of affected versions across three major SQL Server release branches demands priority patching.

RemediationAI

Vendor-released patch: Microsoft has published fixes for all affected branches, so upgrade to SQL Server 2019 GDR build 15.0.2190.7 or CU32 build 15.0.4490.9, SQL Server 2022 GDR build 16.0.1200.5 or CU26 build 16.0.4275.2, and SQL Server 2025 GDR build 17.0.1135.8 or CU8 build 17.0.4085.5, applying the update that matches the servicing branch already installed; details and download links are in the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-67636. Because exploitation requires network reachability to the database endpoint and (per our assessment) a valid connection, the highest-value compensating controls until patching is complete are: block inbound TCP 1433 (and the SQL Server Browser UDP 1434, plus any configured dynamic ports) from untrusted network segments at the host firewall, with the trade-off that legitimate remote clients and administrative tooling must be moved behind a jump host or VPN; restrict SQL logins to the least privilege needed and disable or heavily audit application accounts that connect from semi-trusted segments, accepting the operational cost of credential review; disable unused surface such as xp_cmdshell, CLR integration, and Linked Server configurations, which reduces post-exploitation options but can break legitimate ETL or automation jobs; and take non-production or multi-tenant instances offline or onto dedicated hosts during the patch window, which reduces blast radius at the cost of availability. Re-scan with credentialed vulnerability management against the exact build numbers above rather than relying on registry key or product-name detection, since GDR and CU branches report different build strings for the same product version.

Affected VersionsENISA

Microsoft SQL Server 2025 (CU8) 17.0.0.0 <17.0.4085.5
Microsoft SQL Server 2022 (CU 26) 16.0.0.0 <16.0.4275.2
Microsoft SQL Server 2019 (GDR) 15.0.0 <15.0.2190.7
Microsoft SQL Server 2019 (CU 32) 15.0.0.0 <15.0.4490.9
Microsoft SQL Server 2022 (GDR) 16.0.0 <16.0.1200.5
Microsoft SQL Server 2025 for x64-based Systems (GDR) 17.0.1050.2 <17.0.1135.8

Affected Packages

euvd microsoft_sql_server_2019_cu_32 fix: 15.0.4490.9
euvd microsoft_sql_server_2019_gdr fix: 15.0.2190.7
euvd microsoft_sql_server_2022_cu_26 fix: 16.0.4275.2
euvd microsoft_sql_server_2022_gdr fix: 16.0.1200.5
euvd microsoft_sql_server_2025_cu8 fix: 17.0.4085.5
euvd microsoft_sql_server_2025_for_x64_based_systems_gdr fix: 17.0.1135.8

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 6 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 is CWE-125 (Out-of-bounds Read), a memory-safety flaw in the SQL Server engine's x64 code path in which data is read beyond the bounds of an allocated buffer or index range. Microsoft has chosen to classify the outcome as remote code execution (C:H/I:H/A:H), a severe escalation for an OOB read: achieving code execution typically requires the attacker to first obtain an information disclosure or heap-shaping primitive from the over-read and then turn it into control-flow or data corruption under very specific memory layout conditions, which is why the vendor's vector carries AC:H and our assessment agrees on AC:H. The discrepancy between the published vector's PR:N/S:C and our assessed PR:L/S:U reflects the realistic prerequisite of a working database connection and the fact that a memory-safety bug inside the SQL Server process does not automatically grant control of an underlying hypervisor or host OS. Affected CPEs enumerate Microsoft SQL Server 2019, SQL Server 2022, and SQL Server 2025 on the x64 platform, covering both GDR (security-only) and CU (cumulative update) servicing branches, which is why fixed builds differ per branch. The same underlying code is referenced by ENISA EUVD-2026-73316 and the MSRC update guide entry for CVE-2026-67636; tags mark it primarily as an information-disclosure class issue (consistent with CWE-125) even though the vendor assigns full code-execution impact.

Know when Sql Server 2019 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

NVD PRIMARY 9.0 CRITICAL
AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H
ENISA EUVD HIGH
vuln.today AI 7.5 HIGH

Description says 'authorized attacker,' so PR:L not PR:N; OOB-read-to-RCE steering warrants AC:H; full impact in the SQL Server process gives C:H/I:H/A:H, and scope change is unproven so S:U.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

5
Analysis Updated
Sep 17, 2026 - 20:37 vuln.today
v2 - CVSS changed
Severity Changed
Sep 17, 2026 - 20:22 NVD
HIGH CRITICAL
CVSS changed
Sep 17, 2026 - 20:22 NVD
8.5 (HIGH) 9.0 (CRITICAL)
Patch available
Sep 08, 2026 - 18:35 EUVD
CVE Published
Sep 08, 2026 - 18:18 nvd
HIGH 8.5

DescriptionNVD

Out-of-bounds read in SQL Server allows an authorized attacker to execute code over a network.

Executive ViewAI

Why It Matters

Microsoft SQL Server 2019, 2022, and 2025 on x64 are affected by a critical-severity memory-safety flaw that can, under specific conditions, lead to remote code execution against the database engine. A vendor patch is available, and there is no public exploit identified at time of analysis, but exposed or multi-tenant SQL Server deployments should prioritize remediation because a compromised database engine can enable data theft, integrity loss, and lateral movement into business-critical systems. Leadership should care because these databases often support sensitive customer, financial, and operational data, making patch timing a direct risk-management decision.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.5%
Top 60% exploitable
Prevalence
High
Microsoft SQL Server is widely deployed enterprise database software
Threat Intel
2
1 sources
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Unlikely
Data Quality
6 sources
Confidence: High

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.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.5%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

50
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +45
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: +5

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2026-21262 HIGH POC
8.8 Mar 10

SQL Server 2016-2025 contains an improper access control flaw that allows authenticated network attackers to escalate pr

CVE-2026-67631 CRITICAL
9.8 Sep 08

Heap-based buffer overflow in Microsoft SQL Server 2017, 2019, 2022, and 2025 (x64) can be triggered over the network an

CVE-2026-67378 CRITICAL
9.0 Sep 08

Code execution is possible in Microsoft SQL Server 2019, 2022, and 2025 (x64) through an untrusted pointer dereference i

CVE-2024-37341 CRITICAL
9.8 Sep 10

Microsoft SQL Server Elevation of Privilege Vulnerability. Rated critical severity (CVSS 9.8), this vulnerability is rem

CVE-2024-37980 CRITICAL
9.8 Sep 10

Microsoft SQL Server Elevation of Privilege Vulnerability. Rated critical severity (CVSS 9.8), this vulnerability is rem

CVE-2026-77484 HIGH
8.8 Sep 08

Remote code execution in Microsoft SQL Server 2019, 2022, and 2025 is achievable by an authenticated low-privilege attac

CVE-2026-77482 HIGH
8.8 Sep 08

Heap-based buffer overflow in Microsoft SQL Server 2017 and 2019 enables unauthenticated network attackers to execute ar

CVE-2026-66819 HIGH
8.8 Sep 08

SQL injection in Microsoft SQL Server enables a low-privileged authenticated attacker to escalate database privileges ov

CVE-2026-67368 HIGH
8.8 Sep 08

Privilege escalation in Microsoft SQL Server 2017 through 2025 allows any low-privileged authenticated database user to

CVE-2026-67639 HIGH
8.8 Sep 08

Heap-based buffer overflow in Microsoft SQL Server 2017 through 2025 enables an authenticated low-privilege network atta

CVE-2026-67380 HIGH
8.8 Sep 08

Remote code execution is possible in Microsoft SQL Server 2017 through 2025 via a heap-based buffer overflow (CWE-122) t

CVE-2026-67370 HIGH
8.8 Sep 08

SQL injection in Microsoft SQL Server (versions 2017 through 2025) enables a network-authenticated low-privilege attacke

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy