{"@odata.context":"https://api.msrc.microsoft.com/sug/v2.0/sugodata/v2.0/en-US/$metadata#vulnerability","@odata.count":1,"value":[{"id":"00000000-0000-0000-0000-00003c403795","releaseDate":"2026-11-10T08:00:00-08:00","cveNumber":"CVE-2026-67632","cveTitle":"Microsoft SQL Server Remote Code Execution Vulnerability","releaseNumber":"2026-Nov","vulnType":"Security Vulnerability","latestRevisionDate":"2026-11-10T08:00:00-08:00","description":"

Heap-based buffer overflow in SQL Server allows an authorized attacker to execute code over a network.

\n","cweList":["CWE-122: Heap-based Buffer Overflow"],"cweDetailsListForSearch":["cwe: CWE-122: Heap-based Buffer Overflow","cweUrl: https://cwe.mitre.org/data/definitions/122.html"],"unformattedDescription":"

Heap-based buffer overflow in SQL Server allows an authorized attacker to execute code over a network.

","mitreText":"CVE-2026-67632","mitreUrl":"https://www.cve.org/CVERecord?id=CVE-2026-67632","publiclyDisclosed":"No","exploited":"No","latestSoftwareReleaseId":3,"latestSoftwareRelease":"Exploitation Unlikely","olderSoftwareReleaseId":0,"denialOfService":"N/A","tag":"SQL Server","issuingCna":"Microsoft","issuingCnaId":100000001,"severityId":100000001,"severity":"Important","impactId":100000005,"impact":"Remote Code Execution","langCode":"en-US","baseScore":"8.8","temporalScore":"7.7","vectorString":"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","vectorStringSource":"Microsoft","isMariner":false,"customerActionRequired":true,"customerActionRequiredId":1,"cweDetailsList":[{"keys":["cwe","cweUrl"],"values":["CWE-122: Heap-based Buffer Overflow","https://cwe.mitre.org/data/definitions/122.html"]}],"articles":[{"title":"SQL Server Remote Code Execution Vulnerability","articleType":"100000000","description":"

Heap-based buffer overflow in SQL Server allows an authorized attacker to execute code over a network.

\n","ordinal":10000},{"articleType":"FAQ","description":"

How could an attacker exploit this vulnerability?

\n

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.

\n","ordinal":10000},{"articleType":"FAQ","description":"

How could an attacker exploit this vulnerability?

\n

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.

\n","ordinal":10000},{"articleType":"FAQ","description":"

I am running SQL Server on my system. What action do I need to take?

\n

Update your relevant version of SQL Server using the applicable November 2026 security update listed below.

\n

There are GDR and/or CU (Cumulative Update) updates offered for my version of SQL Server. How do I know which update to use?

\n\n

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.

\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
Update NumberTitleVersionApply if current product version is\u2026This security update also includes servicing releases up through\u2026
5129299SQL Server 2025 CU10+GDR (November GDR 2026)17.0.5045.317.0.4006.2 - 17.0.5035.5KB5125471 - SQL2025 RTM CU10
5132748SQL Server 2025 RTM+GDR (November GDR 2026)17.0.1155.317.0.1000.7 - 17.0.1145.4KB5128492 - Previous SQL2025 RTM GDR
5129300SQL Server 2022 CU27+GDR2 (November GDR 2026)16.0.4315.216.0.4003.1 - 16.0.4305.5KB5126934 - SQL2022 RTM CU27 GDR
5132747SQL Server 2022 RTM+GDR (November GDR 2026)16.0.1220.316.0.1000.6 - 16.0.1210.3KB5128493 - Previous SQL2022 RTM GDR
5132745SQL Server 2019 CU32+GDR (November GDR 2026)15.0.4510.215.0.4003.23 - 15.0.4500.2KB5128494 - Previous SQL2019 RTM CU32 GDR
5132751SQL Server 2019 RTM+GDR (November GDR 2026)15.0.2210.415.0.2000.5 - 15.0.2200.2KB5128495 - Previous SQL2019 RTM GDR
5132746SQL Server 2017 CU31+GDR (November GDR 2026)14.0.3570.214.0.3006.16 - 14.0.3560.2KB5128496 - Previous SQL2017 RTM CU31 GDR
5132749SQL Server 2017 RTM+GDR (November GDR 2026)14.0.2150.214.0.1000.169 - 14.0.2140.2KB5128497 - Previous SQL2017 RTM GDR
\n

What are the GDR and CU update designations and how do they differ?

\n

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.

\n","ordinal":10000}],"revisions":[{"cveNumber":"CVE-2026-67632","version":1,"revisionDate":"2026-11-10T08:00:00-08:00","initialDate":"0001-01-01T00:00:00Z","description":"

Information published.

\n","unformattedDescription":"Information published.","notificationNeeded":false,"notificationSent":false,"sourceId":"4cd043c3-fe8c-f111-93a1-000d3ac5fb71"}]}]}