Microsoft OLE DB provider is widely deployed; remote code execution in this component can impact many Windows/SQL environments and cause enterprise-wide compromise.
CVE-2026-85838
Heap overflow in Microsoft WDAC OLE DB provider allows remote code execution
Is CVE-2026-85838 being exploited?
Not confirmed. CVE-2026-85838 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.72% probability of exploitation in the next 30 days.
How severe is CVE-2026-85838?
CVE-2026-85838 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-85838?
Yes. A fix has been recorded for CVE-2026-85838. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-85838 affect?
CVE-2026-85838 affects Microsoft WDAC OLE DB provider for SQL, Windows systems with WDAC OLE DB provider installed, Applications using OLE DB for SQL connections. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-85838?
Install Microsoft security update immediately; restrict OLE DB access until patched.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via crafted OLE DB requests; attacker can run arbitrary code and fully compromise affected hosts and pivot across the network.
Immediate action required
- affected>= 10.0.14393.0 and < 10.0.14393.9612
- affected>= 10.0.17763.0 and < 10.0.17763.9376
- affected>= 10.0.19044.0 and < 10.0.19044.7807
- affected>= 10.0.19045.0 and < 10.0.19045.7807
- affected>= 10.0.22631.0 and < 10.0.22631.7652
- affected>= 10.0.22631.0 and < 10.0.22631.7652
- affected>= 10.0.26100.0 and < 10.0.26100.9711
- affected>= 10.0.26200.0 and < 10.0.26200.9711
- affected>= 10.0.28000.0 and < 10.0.28000.3231
- affected>= 10.0.26300.0 and < 10.0.26300.9711
- affected>= 6.2.9200.0 and < 6.2.9200.26434
- affected>= 6.3.9600.0 and < 6.3.9600.23470
- affected>= 6.3.9600.0 and < 6.3.9600.23470
- affected>= 6.2.9200.0 and < 6.2.9200.26434
- affected>= 10.0.14393.0 and < 10.0.14393.9612
- affected>= 10.0.14393.0 and < 10.0.14393.9612
- affected>= 10.0.17763.0 and < 10.0.17763.9376
- affected>= 10.0.17763.0 and < 10.0.17763.9376
- affected>= 10.0.20348.0 and < 10.0.20348.5761
- affected>= 10.0.26100.0 and < 10.0.26100.33650
- affected>= 10.0.26100.0 and < 10.0.26100.33650
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
cisa ssvc
- exploitation
- none
- automatable
- no
- technical impact
- total
Assessed by CISA 10 Nov 2026 (SSVC 2.0.3).
timeline
- 10 Nov 2026Published
- 10 Nov 2026CISA SSVC assessment: exploitation none · same day later
- 11 Nov 2026CVE record last updated · 1 day later
- 12 Nov 2026Analysed by vulneraibility.com · 1 day later
- Patchmsrc.microsoft.com /update-guide/vulnerability/CVE-2026-85838
sources
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
- Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.