CVE-2026-67637: Microsoft SQL Server Remote Code Execution Vulnerability
CVE-2026-67637 is a remote code execution vulnerability in Microsoft SQL Server, rated Important by Microsoft, with a CVSS 3.1 base score of 8.8 (High). An attacker can exploit it remotely over the network, with low privileges and without user interaction. Microsoft has not reported exploitation in the wild and rates exploitation as unlikely. Microsoft released the fix on 10 November 2026 in the November 2026 Patch Tuesday, delivered through 8 security updates (KB5132749, KB5132751, KB5132747, KB5132748 and more). It affects 8 products in 1 product family (SQL Server).
Key facts
- CVE ID
- CVE-2026-67637
- Severity
- High CVSS 8.8
- Microsoft severity
- Important
- Impact
- Remote Code Execution
- Exploited in the wild
- No
- Publicly disclosed
- No
- Exploitation likelihood
- Unlikely
- CISA KEV
- Not listed
- Released
- Last updated
- Patch Tuesday
- November 2026 Patch Tuesday
- Product families
- SQL Server
CVSS score and vector
Microsoft scores CVE-2026-67637 at 8.8 (temporal 7.7) using CVSS 3.1. Vector: 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
| Metric | Value |
|---|---|
| Attack vector | Network |
| Attack complexity | Low |
| Privileges required | Low |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality impact | High |
| Integrity impact | High |
| Availability impact | High |
| Exploit code maturity | Unproven |
| Remediation level | Official fix |
| Report confidence | Confirmed |
Description
Heap-based buffer overflow in SQL Server allows an authorized attacker to execute code over a network.
Frequently asked questions (Microsoft)
How could an attacker exploit this vulnerability?
An authenticated attacker with low-level access to an affected server could send a specially crafted request to execute code on the server. User interaction is not required.
How could an attacker exploit this vulnerability?
An authenticated attacker could exploit this vulnerability by connecting to an affected SQL Server and submitting a specially crafted query or request that triggers a memory corruption condition, allowing the attacker to execute code on the server. Authentication is required; user interaction is not required.
I am running SQL Server on my system. What action do I need to take?
Update your relevant version of SQL Server using the applicable November 2026 security update listed below.
There are GDR and/or CU (Cumulative Update) updates offered for my version of SQL Server. How do I know which update to use?
- First, determine your SQL Server version number. For more information, see Microsoft Knowledge Base Article 321185 - How to determine the version, edition, and update level of SQL Server and its components.
- Second, locate the range containing your current version number in the following table. The corresponding update is the one you need to install.
Note: If your version is not represented in the table, review the applicable update's prerequisites and the support status of your SQL Server release before choosing an update. Absence from this table alone does not establish that a version is unsupported.
Update Number
Title
Version
Apply if current product version is…
This security update also includes servicing releases up through…
5129299
SQL Server 2025 CU10+GDR (November GDR 2026)
17.0.5045.3
17.0.4006.2 - 17.0.5035.5
KB5125471 - SQL2025 RTM CU10
5132748
SQL Server 2025 RTM+GDR (November GDR 2026)
17.0.1155.3
17.0.1000.7 - 17.0.1145.4
KB5128492 - Previous SQL2025 RTM GDR
5129300
SQL Server 2022 CU27+GDR2 (November GDR 2026)
16.0.4315.2
16.0.4003.1 - 16.0.4305.5
KB5126934 - SQL2022 RTM CU27 GDR
5132747
SQL Server 2022 RTM+GDR (November GDR 2026)
16.0.1220.3
16.0.1000.6 - 16.0.1210.3
KB5128493 - Previous SQL2022 RTM GDR
5132745
SQL Server 2019 CU32+GDR (November GDR 2026)
15.0.4510.2
15.0.4003.23 - 15.0.4500.2
KB5128494 - Previous SQL2019 RTM CU32 GDR
5132751
SQL Server 2019 RTM+GDR (November GDR 2026)
15.0.2210.4
15.0.2000.5 - 15.0.2200.2
KB5128495 - Previous SQL2019 RTM GDR
5132746
SQL Server 2017 CU31+GDR (November GDR 2026)
14.0.3570.2
14.0.3006.16 - 14.0.3560.2
KB5128496 - Previous SQL2017 RTM CU31 GDR
5132749
SQL Server 2017 RTM+GDR (November GDR 2026)
14.0.2150.2
14.0.1000.169 - 14.0.2140.2
KB5128497 - Previous SQL2017 RTM GDR
What are the GDR and CU update designations and how do they differ?
General Distribution Release (GDR) updates provide security and other broadly applicable critical fixes. Cumulative Updates (CUs) include accumulated fixes for the applicable SQL Server release. Use the version ranges above to select the security update for your installed servicing branch; CU+GDR updates apply to the listed CU branch, while RTM+GDR updates apply to the listed RTM/GDR branch.
Affected products (8)
SQL Server
| Product | Security update | Type | Fixed build | Restart |
|---|---|---|---|---|
| Microsoft SQL Server 2017 for x64-based Systems (GDR) | KB5132749 | Security Update | 14.0.2150.2 | Yes |
| Microsoft SQL Server 2019 for x64-based Systems (GDR) | KB5132751 | Security Update | 15.0.2210.4 | Yes |
| Microsoft SQL Server 2022 for x64-based Systems (GDR) | KB5132747 | Security Update | 16.0.1220.3 | Yes |
| Microsoft SQL Server 2025 for x64-based Systems (GDR) | KB5132748 | Security Update | 17.0.1155.3 | Yes |
| Microsoft SQL Server 2025 for x64-based Systems CU10 | KB5129299 | Security Update | 17.0.5045.3 | Yes |
| Microsoft SQL Server 2022 for x64-based Systems (CU27) | KB5129300 | Security Update | 16.0.4315.2 | Yes |
| Microsoft SQL Server 2019 for x64-based Systems (CU32) | KB5132745 | Security Update | 15.0.4510.2 | Yes |
| Microsoft SQL Server 2017 for x64-based Systems (CU31) | KB5132746 | Security Update | 14.0.3570.2 | Yes |
Security updates (8)
Acknowledgments
- Microsoft Red Team
Revision history
| Version | Date | Description |
|---|---|---|
| 1.0 | Information published. |