dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-26166

HIGH · 8.8 CVSS v3.1 Published 2024-03-12
Fix available
A fix is available. Upgrade to 10.0.10240.20526 / 10.0.14393.6796 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Microsoft WDAC OLE DB provider for SQL Server Remote Code Execution Vulnerability

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a Remote Code Execution vulnerability in the Microsoft Windows Data Access Components (WDAC) OLE DB provider for SQL Server. An attacker could exploit this by sending specially crafted packets to a vulnerable SQL Server instance that uses the WDAC OLE DB provider, potentially allowing execution of arbitrary code with the privileges of the SQL Server service account.

MitigationApply the Microsoft security updates released in February 2024 (KB5002537 and related patches) to all affected SQL Server installations. As a defense-in-depth measure, restrict network access to SQL Server ports and ensure the service runs with minimal required privileges.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:< 10.0.10240.20526
Windows 10 1607Operating system
Affected:< 10.0.14393.6796
Windows 10 1809Operating system
Affected:< 10.0.17763.5576
Windows 10 21h2Operating system
Affected:< 10.0.19044.4170
Windows 10 22h2Operating system
Affected:< 10.0.19045.4170
Windows 11 21h2Operating system
Affected:< 10.0.22000.2836
Windows 11 22h2Operating system
Affected:< 10.0.22621.3296
Windows 11 23h2Operating system
Affected:< 10.0.22631.3296

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Windows build version
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to see the installed Windows build number
    Affected if Build number falls below 10.0.10240.20526 (Win10 1507), 10.0.14393.6796 (Win10 1607), 10.0.17763.5576 (Win10 1809), 10.0.19044.4170 (Win10 21h2), 10.0.19045.4170 (Win10 22h2), 10.0.22000.2836 (Win11 21h2), 10.0.22621.3296 (Win11 22h2), or 10.0.22631.3296 (Win11 23h2)
  2. Verify SQL Server installation using OLE DB provider
    Check for SQL Server instances and identify if they use the WDAC OLE DB provider (SQLOLEDB) for connections. Look in SQL Server configuration or connection strings for 'Provider=SQLOLEDB' or 'SQLOLEDB' references
    Affected if SQL Server is configured to use the SQLOLEDB OLE DB provider from WDAC for data connections
  3. Check for vulnerable WDAC OLE DB component
    Locate the sqloledb.dll file on the system (typically in C:\Windows\System32\ or C:\Windows\SysWOW64\ for 32-bit on 64-bit) and check its file version properties
    Affected if The sqloledb.dll exists and its version is older than the patched versions corresponding to the February 2024 security updates

A system is affected if it runs an unpatched Windows 10/11 version within the affected build ranges AND has SQL Server using the WDAC OLE DB provider (SQLOLEDB) for SQL Server connections.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.10240.20526 / 10.0.14393.6796 / 10.0.17763.5576 or later
Fixed in 10.0.10240.2052610.0.14393.679610.0.17763.5576
Interim mitigation

Apply the Microsoft security updates released in February 2024 (KB5002537 and related patches) to all affected SQL Server installations. As a defense-in-depth measure, restrict network access to SQL Server ports and ensure the service runs with minimal required privileges.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20526+ | Windows 10 1607: 10.0.14393.6796+ | Windows 10 1809: 10.0.17763.5576+ | Windows 10 21h2: 10.0.19044.4170+ | Windows 10 22h2: 10.0.19045.4170+ | Windows 11 21h2: 10.0.22000.2836+ | Windows 11 22h2: 10.0.22621.3296+ | Windows 11 23h2: 10.0.22631.3296+

  1. Verify current Windows version by running 'winver' or 'systeminfo' to confirm the installed build number
  2. Open Settings > Windows Update and check for updates, or manually download the security update from the Microsoft Update Catalog (search for CVE-2024-26166)
  3. Install the March 2024 or later security update for your Windows version
  4. Restart the system after applying the update
  5. Verify the update was installed successfully by checking installed updates via 'appwiz.cpl' or using 'Get-HotFix' in PowerShell
Caveat Standard Windows security update; minimal risk of breaking changes for this cumulative update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA2.0 h
22.0 hours of engineering $3,800
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26166 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-26166 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data