Microsoft rates the vulnerability Important, with a CVSS base score of 8.8. User interaction is required, but that requirement should not obscure the practical risk: a connection to an attacker-controlled server can become a route to code execution on the connecting system.
What Microsoft’s advisory establishes
The Microsoft Security Response Center identifies the issue as follows:
| Field | Official value |
|---|---|
| CVE | CVE-2026-85839 |
| Title | Microsoft WDAC OLE DB provider for SQL Remote Code Execution Vulnerability |
| Severity | Important |
| CVSS base score | 8.8 |
| CVSS temporal score | 7.7 |
| Weakness | CWE-122 |
| Exploitation assessment | Exploitation Less Likely |
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Microsoft’s status fields state:
- Publicly disclosed: No
- Exploited: No
- Customer action required: Yes
The vulnerability is a heap-based buffer overflow in Microsoft WDAC OLE DB provider for SQL that allows an unauthorized attacker to execute code over a network.
Microsoft describes a specific attack sequence: an attacker hosts a malicious server and convinces a user to connect from an affected client. When that client processes the server’s response, the attacker could execute code on the client system. User interaction is required.
That distinction matters for administrators assessing exposure. The advisory describes the connecting client as the execution target; it should not be read simply as an attack against a server accepting incoming connections.
What the score means for patch prioritization
The supplied vector describes a network attack with low attack complexity, no required privileges, and required user interaction. It also assigns high potential impact to confidentiality, integrity, and availability, with unchanged scope.
Those characteristics explain why this deserves attention even alongside Microsoft’s Exploitation Less Likely assessment. The assessment and the impact rating answer different questions: the former addresses exploitation likelihood, while the latter describes the potential consequences of successful exploitation.
The practical implication of Microsoft’s attack description is to include systems that make relevant outbound connections in the patch review. Looking only at systems exposed to unsolicited inbound traffic would miss the client-side scenario described in the advisory.
Complete affected-product and remediation list
The following remediation values reproduce Microsoft’s product-specific KB-to-build mappings. Each fixed build is the vendor’s specified target for that product.
Windows 10
- For Windows 10 Version 1607 for 32-bit Systems (x86), install KB5126868 to reach fixed build 10.0.14393.9612.
- For Windows 10 Version 1607 for x64-based Systems, install KB5126868 to reach fixed build 10.0.14393.9612.
- For Windows 10 Version 1809 for 32-bit Systems (x86), install KB5126651 to reach fixed build 10.0.17763.9376.
- For Windows 10 Version 1809 for x64-based Systems, install KB5126651 to reach fixed build 10.0.17763.9376.
- For Windows 10 Version 21H2 for 32-bit Systems (x86), install KB5126657 to reach fixed build 10.0.19044.7807.
- For Windows 10 Version 21H2 for ARM64-based Systems, install KB5126657 to reach fixed build 10.0.19044.7807.
- For Windows 10 Version 21H2 for x64-based Systems, install KB5126657 to reach fixed build 10.0.19044.7807.
- For Windows 10 Version 22H2 for 32-bit Systems (x86), install KB5126657 to reach fixed build 10.0.19045.7807.
- For Windows 10 Version 22H2 for ARM64-based Systems, install KB5126657 to reach fixed build 10.0.19045.7807.
- For Windows 10 Version 22H2 for x64-based Systems, install KB5126657 to reach fixed build 10.0.19045.7807.
Windows 11
- For Windows 11 Version 23H2 for ARM64-based Systems, install KB5126653 to reach fixed build 10.0.22631.7652.
- For Windows 11 Version 23H2 for x64-based Systems, install KB5126653 to reach fixed build 10.0.22631.7652.
- For Windows 11 Version 24H2 for ARM64-based Systems, install KB5127648 to reach fixed build 10.0.26100.9711.
- For Windows 11 Version 24H2 for x64-based Systems, install KB5127648 to reach fixed build 10.0.26100.9711.
- For Windows 11 Version 25H2 for ARM64-based Systems, install KB5127648 to reach fixed build 10.0.26200.9711.
- For Windows 11 Version 25H2 for x64-based Systems, install KB5127648 to reach fixed build 10.0.26200.9711.
- For Windows 11 Version 26H1 for ARM64-based Systems, install KB5127646 to reach fixed build 10.0.28000.3231.
- For Windows 11 version 26H1 for x64-based Systems, install KB5127646 to reach fixed build 10.0.28000.3231.
- For Windows 11 Version 26H2 for ARM64-based Systems, install KB5127648 to reach fixed build 10.0.26300.9711.
- For Windows 11 Version 26H2 for x64-based Systems, install KB5127648 to reach fixed build 10.0.26300.9711.
Windows Server
- For Windows Server 2012 (Server Core installation) (x64), install KB5126835 to reach fixed build 6.2.9200.26434.
- For Windows Server 2012 (x64), install KB5126835 to reach fixed build 6.2.9200.26434.
- For Windows Server 2012 R2 (Server Core installation) (x64), install KB5126836 to reach fixed build 6.3.9600.23470.
- For Windows Server 2012 R2 (x64), install KB5126836 to reach fixed build 6.3.9600.23470.
- For Windows Server 2016 (Server Core installation) (x64), install KB5126868 to reach fixed build 10.0.14393.9612.
- For Windows Server 2016 (x64), install KB5126868 to reach fixed build 10.0.14393.9612.
- For Windows Server 2019 (Server Core installation) (x64), install KB5126651 to reach fixed build 10.0.17763.9376.
- For Windows Server 2019 (x64), install KB5126651 to reach fixed build 10.0.17763.9376.
- For Windows Server 2022 (Server Core installation) (x64), install KB5126655 to reach fixed build 10.0.20348.5761.
- For Windows Server 2022 (x64), install KB5126655 to reach fixed build 10.0.20348.5761.
- For Windows Server 2025 (Server Core installation) (x64), install KB5126646 to reach fixed build 10.0.26100.33650.
- For Windows Server 2025 (x64), install KB5126646 to reach fixed build 10.0.26100.33650.
Avoid these patch-verification mistakes
A comparison of Microsoft’s mappings reveals two useful checks for deployment reporting.
First, a shared KB does not mean a shared resulting build. KB5127648 maps to fixed builds 10.0.26100.9711, 10.0.26200.9711, and 10.0.26300.9711 across the listed Windows 11 branches. Similarly, KB5126657 maps to 10.0.19044.7807 and 10.0.19045.7807 across the listed Windows 10 branches. A compliance report should therefore match the product branch as well as the update identifier.
Second, a similar build prefix does not make updates interchangeable. Windows 11 Version 24H2 for x64-based Systems maps to KB5127648 and 10.0.26100.9711, while Windows Server 2025 (x64) maps to KB5126646 and 10.0.26100.33650. Both begin with 10.0.26100, but Microsoft specifies different updates and fixed builds.
These are operational conclusions drawn from the official mappings, not additional vulnerability claims. They provide a straightforward guardrail: verify product, architecture, KB, and resulting build together, rather than treating any one field as sufficient.
What administrators should do
Use the affected-product list to identify applicable systems, deploy each product’s specified update through the organization’s established patch process, and validate the resulting build against its matching entry. Include the listed Server Core installations rather than excluding them from the review.
Microsoft’s attack description also supports a targeted user reminder: do not connect affected clients to unfamiliar servers at someone else’s prompting. That caution addresses the interaction required in the documented scenario; it is not a substitute for installing the fix.
The bottom line is clear: CVE-2026-85839 requires customer action despite its lower exploitation-likelihood assessment. Patch the affected connecting systems, and verify the correct build for each branch—not merely that an update deployment was scheduled.
References
- Official MSRC or vendor evidence api.msrc.microsoft.com
- Official MSRC or vendor evidence msrc.microsoft.com
- Official MSRC or vendor evidence api.msrc.microsoft.com