The short version: Microsoft says a heap memory flaw lets an attacker who already has some authorized access run code over the network. Supported SQL Server releases from 2017 through 2025 are affected, and Microsoft shipped fixes on November 10.
What Microsoft disclosed
Microsoft's Security Update Guide titles the issue "Microsoft SQL Server Remote Code Execution Vulnerability." It describes it this way: Heap-based buffer overflow in SQL Server allows an authorized attacker to execute code over a network. The weakness is classed as CWE-122, a heap-based buffer overflow. In plain terms, SQL Server writes more data into a heap memory block than the block can hold. Overflows like this are a well-known route to running attacker-supplied code.
The CVSS 3.1 base score is 8.8, rated High. Here is what the vector string (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) means:
- Network attack vector: the attacker doesn't need local access to the server.
- Low complexity: no unusual conditions have to line up.
- Low privileges required: the attacker needs some level of authorized access.
- No user interaction: nobody has to click or open anything.
- High impact on confidentiality, integrity and availability.
That "low privileges" requirement is the key detail. This is not described as an unauthenticated, anyone-on-the-internet flaw. Microsoft's description doesn't say what privilege level or database permissions an attacker needs, and it doesn't describe how an exploit would work. Don't read more into it than that. In practice, the threat model is an account that can already reach the instance and log in, such as a compromised application login or a low-privilege user who should never get operating-system-level code execution.
Section summary: a heap overflow in SQL Server, scored 8.8 High. An attacker needs authorized access but no user interaction, and success could mean full compromise of the instance.
Exploitation status
At publication, the vulnerability data didn't show this bug being exploited. The CVSS temporal metrics on the record (E:U/RL:O/RC:C) mark exploit code maturity as unproven, an official fix as available, and the report as confirmed by the vendor. Senserva, a third-party patch-tracking site, lists CVE-2026-67391 as High | 8.8 | - | No in the "Exploited" column for KB5132747. Its entries for other packages put the EPSS probability below 1%.
That status can change. Microsoft confirmed the vulnerability, and patch releases tend to attract reverse engineers who compare the fixed and unfixed code. The calm status is a reason to patch on a schedule, not a reason to skip patching.
It's one of several SQL Server fixes this month
CVE-2026-67391 isn't the only database engine fix this month. The vulnerability tracker CVELogic lists sibling CVEs published the same day with the same wording, including CVE-2026-67637, CVE-2026-67632 and CVE-2026-67374. Each is described as a Heap-based buffer overflow in SQL Server allows an authorized attacker to execute code over a network. Each also scores 8.8. The same tracker lists an elevation-of-privilege flaw (CVE-2026-67387) and an information disclosure bug (CVE-2026-67382).
According to Senserva, the SQL Server 2017 GDR package alone patches 44 CVEs (max CVSS 9.8), released 2026-11-10. So for most shops, CVE-2026-67391 is one more reason to install this month's SQL Server update, and the decision to patch shouldn't depend on this CVE alone.
Section summary: no reported exploitation at the time of writing, but several other high-severity SQL Server engine fixes arrived on the same day, so this is a bigger patch than usual.
Affected builds, KB numbers and fixed versions
The affected entries cover eight x64 SQL Server servicing tracks across 2017, 2019, 2022 and 2025. As with every SQL Server security release, you need to match your servicing branch (GDR or cumulative update) as well as your major version. A CU-branch server needs the CU-branch security update, not the GDR one.
Microsoft's Security Update Guide pairs most of the packages with branches. Its table maps 5129299 | SQL Server 2025 CU10+GDR (November GDR 2026) | 17.0.5045.3 | 17.0.4006.2 - 17.0.5035.5. It also lists KB5132748 for SQL Server 2025 RTM+GDR, KB5129300 for SQL Server 2022 CU27+GDR, KB5132747 for SQL Server 2022 RTM+GDR, KB5132751 for SQL Server 2019 RTM+GDR, and KB5132749 for SQL Server 2017 RTM+GDR.
| Product / servicing track | Affected range in the CVE record | Fixed build | Security update |
|---|---|---|---|
| SQL Server 2025 CU10 | 17.0.4006.0 to below 17.0.5045.3 | 17.0.5045.3 | KB5129299 |
| SQL Server 2025 GDR | 17.0.1050.2 to below 17.0.1155.3 | 17.0.1155.3 | KB5132748 |
| SQL Server 2022 CU27 | 16.0.4003.1 to below 16.0.4315.2 | 16.0.4315.2 | KB5129300 |
| SQL Server 2022 GDR | 16.0.0 to below 16.0.1220.3 | 16.0.1220.3 | KB5132747 |
| SQL Server 2019 CU32 | 15.0.4003.23 to below 15.0.4510.2 | 15.0.4510.2 | Check the Security Update Guide (see note) |
| SQL Server 2019 GDR | 15.0.0 to below 15.0.2210.4 | 15.0.2210.4 | KB5132751 |
| SQL Server 2017 CU31 | 14.0.3006.16 to below 14.0.3570.2 | 14.0.3570.2 | Check the Security Update Guide (see note) |
| SQL Server 2017 GDR | 14.0.0 to below 14.0.2150.2 | 14.0.2150.2 | KB5132749 |
The record lists eight KBs in total. Two of them, KB5132745 and KB5132746, cover the 2019 CU32 and 2017 CU31 tracks, but the material reviewed here doesn't firmly say which is which. Senserva labels KB5132746 a SQL Server 2017 update, which would leave KB5132745 for 2019 CU32. Treat that as a lead and confirm it in Microsoft's Security Update Guide before you deploy.
Microsoft's table also lists an "applicable" source range for each package, and these don't always match the CVE record's ranges exactly. For example, Microsoft says the SQL Server 2025 RTM+GDR package applies to builds 17.0.1000.7 through 17.0.1145.4. The CVE record starts that affected range at 17.0.1050.2. Use Microsoft's applicable range to choose the package. Use the fixed build number to check that the update worked.
How to patch, step by step
- Find every instance. That includes named instances, developer and test boxes, and SQL Server bundled with line-of-business apps. Instances you've forgotten about are the ones still unpatched next spring.
- Record the full build number. In SQL Server Management Studio or
sqlcmd, runSELECT SERVERPROPERTY('ProductVersion'), SERVERPROPERTY('ProductLevel'), SERVERPROPERTY('ProductUpdateLevel');or simplySELECT @@VERSION;. A build in the 16.0.1xxx range is on the 2022 GDR branch. A build in the 16.0.4xxx range is on the CU branch. - Match the build to its branch using the table above, then confirm the right package in Microsoft's Security Update Guide.
- Check the known issues first. Senserva notes that for KB5129300 (SQL Server 2022 CU27+GDR), Microsoft lists 1 known issue for this update. Separately, Releasebot's SQL Server 2022 release notes describe an issue where enabling trace flag 4696 opts out of a code change. With that flag on, monitoring queries that query sys.dm_exec_requests or sys.sysprocesses on secondary replicas might return error 976 or error 978. The material reviewed doesn't confirm which package that note belongs to. If you run Always On availability groups with replica monitoring, read the KB article before you start the maintenance window.
- Plan for a service restart. For availability groups and failover clusters, patch secondary replicas or passive nodes first, fail over, then patch the former primary.
- Check the result. Run the version query again and confirm the build is at or above the fixed build for your branch.
What to prioritize while patches roll out
Microsoft's advisory data lists no workaround or configuration-based mitigation for CVE-2026-67391. Firewall rules, disabled features and similar measures are not confirmed substitutes for the update. Some sensible steps follow from the requirement for authorized access. They aren't official Microsoft mitigations for this CVE:
- Patch first the instances reachable from broad networks, or those with many logins, such as shared application databases and reporting servers.
- Review who can log in. Remove dormant SQL logins, check over-broad Windows group grants, and rotate application credentials that may be stored in plain text.
- Watch for unusual authentication, especially low-privilege accounts suddenly connecting from new hosts.
Some might argue that a flaw requiring authentication can wait. The counterargument is that attackers often obtain credentials early, through phishing, leaked connection strings or a compromised web app, and then look for exactly this kind of jump from a basic login to running code on the server.
The bottom line
CVE-2026-67391 is a confirmed, patched, high-severity SQL Server bug that requires an authenticated attacker. It hasn't been reported as exploited. It arrived alongside several other high-severity SQL Server fixes in the same November release, which is the stronger reason to install this month's update. Find your instances, match each build to its GDR or CU branch, apply the matching KB and confirm the new build number.
References
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-67391/ msrc.microsoft.com
- KB5132749: SQL Server 2017 Security Update (November 2026) senserva.com
- KB5132747: SQL Server 2022 Security Update (November 2026) senserva.com