Abstract illustration of connected devices separated by a protected security boundary.
Microsoft has issued fixes for CVE-2026-85838, a remote code execution vulnerability in the Microsoft WDAC OLE DB provider for SQL affecting Windows desktop and server systems. Microsoft rates the issue Important, with a CVSS base score of 8.8. The attack requires user interaction: an attacker must persuade someone using an affected client to connect to a malicious server.

For administrators, the key distinction is where execution happens. Microsoft’s described attack targets the connecting client when it processes the server’s response. Remediation planning therefore needs to cover affected Windows machines making those connections, not simply the machines hosting databases.

Abstract illustration of connected devices separated by a protected security boundary. What Microsoft’s advisory establishes​

The Microsoft Security Response Center identifies the issue as Microsoft WDAC OLE DB provider for SQL Remote Code Execution Vulnerability.

FieldMicrosoft advisory value
CVECVE-2026-85838
SeverityImportant
CVSS base score8.8
CVSS temporal score7.7
WeaknessCWE-122 — Heap-based Buffer Overflow
Exploitation assessmentExploitation Less Likely

The complete supplied CVSS vector is:

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 reported status fields are:

  • Publicly disclosed: No
  • Exploited: No
  • Customer action required: Yes

Microsoft describes a heap-based buffer overflow in Microsoft WDAC OLE DB provider for SQL that allows an unauthorized attacker to execute code over a network.

The advisory’s exploitation scenario has three parts:

  1. An attacker hosts a malicious server.
  2. The attacker convinces a user to connect to that server from an affected client.
  3. When the client processes the server’s response, the attacker could execute code on the client system.

User interaction is required. The network attack vector should not be read as a claim that merely exposing a machine to a network triggers this vulnerability. Microsoft’s scenario specifically involves a user making the connection.

The vector also describes low attack complexity, no required attacker privileges, unchanged scope, and high potential impacts on confidentiality, integrity, and availability. Those characteristics explain why the issue deserves patching attention even though Microsoft assesses exploitation as less likely. That assessment is a prioritization input, not a substitute for remediation.

A practical patch-verification trap​

Microsoft’s affected-product mappings show why checking only a KB number is not enough to establish the expected fixed build across a mixed estate.

For example, KB5127648 maps to three different Windows desktop builds:

  • 10.0.26100.9711 for the listed 24H2 systems.
  • 10.0.26200.9711 for the listed 25H2 systems.
  • 10.0.26300.9711 for the listed 26H2 systems.

Meanwhile, the listed server systems using the 10.0.26100 build branch have a different mapping: KB5126646, with fixed build 10.0.26100.33650.

The operational conclusion, drawn from those Microsoft mappings, is straightforward: match product, release, architecture, KB, and full fixed build together. Neither a shared KB nor a shared build prefix makes different product entries interchangeable.

The complete product-specific remediation instructions follow. Each sentence includes the affected product, its update, and Microsoft’s fixed-build target.

Windows desktop remediation​

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 remediation​

The affected-product list includes both Server Core and other listed server installations. Server Core entries therefore belong in the remediation inventory rather than being excluded on installation type alone.

  • 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.

What administrators should prioritize​

The advisory and update mappings support three practical decisions:

  1. Include connecting clients in the patch scope. The described code execution occurs on the system processing the malicious server response. A database-host-only patch campaign would miss that distinction.
  2. Validate against the exact product entry. Record the applicable KB and full fixed build for each affected release and architecture. Shared update identifiers do not imply identical build targets.
  3. Treat connection requests as part of the exposure assessment. Because the attack depends on persuading a user to connect to an attacker-controlled server, workflows involving unfamiliar server destinations deserve attention during patch prioritization.

That final point is an operational inference from Microsoft’s attack scenario, not a separate vendor workaround. Avoiding untrusted destinations does not replace the listed security updates.

The bottom line: CVE-2026-85838 is a user-interaction-dependent remote code execution vulnerability with fixes spanning Windows desktop and server releases. Apply the product-specific update, verify the corresponding full fixed build, and keep the connecting client—not just the database host—at the center of the remediation plan.

 

References

  1. Official MSRC or vendor evidence api.msrc.microsoft.com
  2. Official MSRC or vendor evidence msrc.microsoft.com
  3. Official MSRC or vendor evidence api.msrc.microsoft.com