dbcve.org
Ole Db Driver For Sql ServerApplication · Microsoft

CVE-2024-28926

HIGH · 8.8 CVSS v3.1 Developing Published 2024-04-09
Fix available
A fix is available. Upgrade to 15.0.2110.4 / 15.0.4360.2 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 OLE DB Driver 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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-07-31.

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
Ole Db Driver For Sql ServerApplication
Affected:>= 18.0.2, < 18.7.0002.0>= 19.0.0, < 19.3.0003.0
Sql Server 2019Application
Affected:>= 15.0.2000.5, < 15.0.2110.4>= 15.0.4003.23, < 15.0.4360.2
Sql Server 2022Application
Affected:>= 16.0.1000.6, < 16.0.1115.1>= 16.0.4003.1, < 16.0.4120.1

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

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 15.0.2110.4 / 15.0.4360.2 / 16.0.1115.1 or later
Fixed in 15.0.2110.415.0.4360.216.0.1115.1
Recommended fix High confidence

OLE DB Driver 18.7.0002.0 / 19.3.0003.0; SQL Server 2019 CU22 (15.0.2110.4) or CU34 (15.0.4360.2); SQL Server 2022 CU9 (16.0.1115.1) or CU16 (16.0.4120.1)

  1. 1. Identify the exact version of Microsoft OLE DB Driver for SQL Server or SQL Server instance by running 'SELECT @@VERSION' or checking the installed program version.
  2. 2. For OLE DB Driver: If using version 18.x, upgrade to version 18.7.0002.0 or later; if using version 19.x, upgrade to version 19.3.0003.0 or later.
  3. 3. For SQL Server 2019: If running build 15.0.2000.5 through 15.0.2110.4, apply Cumulative Update 22 (CU22) which includes build 15.0.2110.4 or later; if running build 15.0.4003.23 through 15.0.4360.2, apply Cumulative Update 34 (CU34) which includes build 15.0.4360.2 or later.
  4. 4. For SQL Server 2022: If running build 16.0.1000.6 through 16.0.1115.1, apply Cumulative Update 9 (CU9) which includes build 16.0.1115.1 or later; if running build 16.0.4003.1 through 16.0.4120.1, apply Cumulative Update 16 (CU16) which includes build 16.0.4120.1 or later.
  5. 5. Download the appropriate update from the Microsoft Update Catalog or use Windows Update after backing up databases.
  6. 6. Test the update in a non-production environment before deploying to production.
Caveat Cumulative Updates are generally low-risk but always test in non-production first; review release notes for any known issues

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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