dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2024-26210

HIGH · 8.8 CVSS v3.1 Published 2024-04-09
Fix available
A fix is available. Upgrade to 10.0.10240.20596 / 10.0.14393.6897 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 Microsoft's WDAC (Windows Defender Application Control) OLE DB provider for SQL Server. The vulnerability allows an attacker to execute arbitrary code on affected systems through the OLE DB provider interface, likely via specially crafted SQL queries or data packets.

MitigationApply Microsoft security updates for CVE-2024-26210 immediately. Until patches are applied, limit network exposure of SQL Server systems and disable the WDAC OLE DB provider if not required.

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.20596
Windows 10 1607Operating system
Affected:< 10.0.14393.6897
Windows 10 1809Operating system
Affected:< 10.0.17763.5696
Windows 10 21h2Operating system
Affected:< 10.0.19044.4291
Windows 10 22h2Operating system
Affected:< 10.0.19045.4291
Windows 11 21h2Operating system
Affected:< 10.0.22000.2899
Windows 11 22h2Operating system
Affected:< 10.0.22621.3447
Windows 11 23h2Operating system
Affected:< 10.0.22631.3447

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 version against affected ranges
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' and compare the displayed version to the affected version ranges: Windows 10 1507 < 10.0.10240.20596, 1607 < 10.0.14393.6897, 1809 < 10.0.17763.5696, 21h2 < 10.0.19044.4291, 22h2 < 10.0.19045.4291; Windows 11 21h2 < 10.0.22000.2899, 22h2 < 10.0.22621.3447, 23h2 < 10.0.22631.3447
    Affected if The installed Windows version matches one of the affected versions and is below the fixed build number
  2. Verify WDAC OLE DB provider is present
    Check for the presence of the Windows Defender Application Control OLE DB provider files on the system - typically this provider ships with SQL Server or Windows SQL components
    Affected if The WDAC OLE DB provider files exist on the system and the Windows version is in the affected range
  3. Confirm SQL Server OLE DB provider is enabled
    Review SQL Server configuration or Windows services to determine if the OLE DB provider interface is active and accessible
    Affected if SQL Server with OLE DB provider support is running and accessible, and the Windows version is in the affected range

A user is affected if their Windows version falls within the specified affected build ranges AND they have the WDAC OLE DB provider for SQL Server installed and enabled on their system.

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.20596 / 10.0.14393.6897 / 10.0.17763.5696 or later
Fixed in 10.0.10240.2059610.0.14393.689710.0.17763.5696
Interim mitigation

Apply Microsoft security updates for CVE-2024-26210 immediately. Until patches are applied, limit network exposure of SQL Server systems and disable the WDAC OLE DB provider if not required.

Recommended fix High confidence

Upgrade Windows to the latest cumulative security update for your specific Windows release, meeting or exceeding the fixed build numbers listed above

  1. Identify the current Windows version by running 'winver' or checking Settings > System > About
  2. Note the full build number (e.g., 10.0.19045.xxxx)
  3. Determine which Windows release category applies (10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 21h2/22h2/23h2)
  4. Open Windows Update (Settings > Update & Security > Windows Update) and check for available updates
  5. Install all cumulative security updates to reach a build number at or above the fixed version for your release: Windows 10 1507: 10.0.10240.20596 | Windows 10 1607: 10.0.14393.6897 | Windows 10 1809: 10.0.17763.5696 | Windows 10 21h2: 10.0.19044.4291 | Windows 10 22h2: 10.0.19045.4291 | Windows 11 21h2: 10.0.22000.2899 | Windows 11 22h2: 10.0.22621.3447 | Windows 11 23h2: 10.0.22631.3447
  6. Verify the installed version after updating matches or exceeds the required fixed build number
Caveat Standard Windows update risks apply (potential for compatibility issues with legacy applications; backup recommended)

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
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26210 — 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-26210 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