Skip to main content

Windows OLE DB CVE-2026-70210

| EUVDEUVD-2026-99609 HIGH
Heap-based Buffer Overflow (CWE-122)
2026-10-13 secure@microsoft.com GHSA-7733-39jr-3jg2
8.8
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Deliver crafted OLE DB file or data source
  2. Delivery
    Victim opens file or connects
  3. Exploit
    Trigger heap overflow in OLE DB parser
  4. Execution
    Corrupt heap memory
  5. Impact
    Execute code / elevate privileges

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the Windows OLE DB component to process attacker-supplied data - typically the victim opening a malicious file or establishing a connection to an attacker-controlled data source (e.g., a crafted database/connection target parsed by an OLE DB provider). The CVSS vector's UI:R confirms user interaction is MANDATORY, which is the primary limiting factor: there is no fully autonomous, zero-click network path. PR:N means no prior authentication is needed on the target. The flaw affects default Windows installations across Windows 10/11 (multiple versions) and Windows Server 2012 through 2025, including Server Core, so no non-default configuration is required beyond the victim action.

Impact

This is a genuine high-priority patch item but not an emergency. The CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R) reflects a network-reachable, unauthenticated flaw with low attack complexity and full confidentiality, integrity, and availability impact - a serious combination. However, multiple lower-pressure signals temper the urgency: CISA's SSVC decision framework rates Exploitation as 'none' and Automatable as 'no' (only Technical Impact is 'total'), the CVE is NOT on the CISA KEV list, EPSS data was not provided, and no public proof-of-concept is referenced. A notable conflict exists between the one-line description, which frames this as elevation of privilege ('allows an unauthorized attacker to elevate privileges over a network'), and the CVSS vector, which reads like a user-interaction-driven remote code execution / client-side attack (UI:R with S:U and C:H/I:H/A:H). This EoP-vs-RCE wording mismatch should be verified against the Microsoft MSRC advisory before finalizing categorization. Overall: prioritize because the affected product is ubiquitous and the impact is total, but the requirement for user interaction and the 'no exploitation / not automatable' SSVC rating argue against treating it as actively weaponized.

Exploit ScenarioDerived

An attacker lures a victim into opening a crafted file or connecting to an attacker-controlled data source that is parsed by the Windows OLE DB provider, triggering a heap-based buffer overflow (CWE-122). Successful corruption of heap memory lets the attacker run code or gain elevated privileges in the victim's context. No public exploit code is identified at time of analysis, and the CVSS vector's UI:R means the victim must perform an action for the attack to succeed.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.8% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Privilege escalation in Windows OLE DB allows an unauthenticated remote attacker to elevate to SYSTEM by inducing a victim to open a crafted file or connect to an attacker-controlled data source that a vulnerable OLE DB provider parses, causing a heap-based buffer overflow (CWE-122). The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, score 8.8) confirms authentication is not required, but user interaction is mandatory - there is no zero-click network path, which is the main limiting factor. All default Windows installations are affected across Windows 10, Windows 11 (22H2 through 26H2) and Windows Server 2012 through 2025 including Server Core; there is no public exploit identified at time of analysis and CISA SSVC records exploitation as none, so this is a high-priority patch item rather than an emergency.

RemediationAI

Vendor-released patch: Microsoft has published fixes for CVE-2026-70210 via the MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70210); apply the current cumulative update for your build - Windows 11 26H1 10.0.28000.3231, 26H2 10.0.26300.9711, 25H2 10.0.26200.9711, 24H2 10.0.26100.9711, 23H2 10.0.22631.7652; Windows 10 22H2/21H2 10.0.19044.7807, 1809 10.0.17763.9376, 1607 10.0.14393.9612; Windows Server 2025 10.0.26100.33650, Server 2022 10.0.20348.5761, Server 2019 10.0.17763.9376, Server 2016 10.0.14393.9612, Server 2012 R2 6.3.9600.23470, Server 2012 6.2.9200.26434 - and prioritize internet-facing and multi-user systems (RDS/Citrix, servers hosting data-integration or reporting workloads) since exploitation only requires a victim to open a malicious file or be steered to an attacker-controlled data source. Because no vendor workaround exists that removes the vulnerable parser, compensating controls must target the delivery vector: enforce Mark-of-the-Web and Protected View / Attachment Manager on files reaching users, strip or quarantine high-risk OLE DB connection files and database artifacts at the mail gateway and web proxy, and block outbound connections from workstations to untrusted data-source endpoints (side effect: can break legitimate remote database and reporting connectivity, so scope by destination allowlist). Do not attempt to unregister OLE DB providers on production servers as a general mitigation - many line-of-business and management tools depend on them and removal causes broad application failures; if a temporary block is required, restrict it to non-essential providers on high-risk endpoints only. Given SSVC exploitation: none and no public exploit identified at time of analysis, treat this as a scheduled but high-priority patch cycle item rather than an emergency out-of-band deployment, and monitor the MSRC advisory for any change in exploitability status.

Affected VersionsENISA

Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows Server 2012 6.2.9200.0 <6.2.9200.26434
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7807
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9612
Windows Server 2019 10.0.17763.0 <10.0.17763.9376
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26434
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23470
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows Server 2022 10.0.20348.0 <10.0.20348.5761
Windows 10 Version 22H2 10.0.19045.0 <10.0.19044.7807
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23470
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9612
Windows Server 2016 10.0.14393.0 <10.0.14393.9612
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9612
euvd windows_10_version_1809 fix: 10.0.17763.9376
euvd windows_10_version_21h2 fix: 10.0.19044.7807
euvd windows_10_version_22h2 fix: 10.0.19044.7807
euvd windows_11_version_23h2 fix: 10.0.22631.7652
euvd windows_11_version_24h2 fix: 10.0.26100.9711
euvd windows_11_version_25h2 fix: 10.0.26200.9711
euvd windows_11_version_26h1 fix: 10.0.28000.3231
euvd windows_11_version_26h2 fix: 10.0.26300.9711
euvd windows_server_2012 fix: 6.2.9200.26434
euvd windows_server_2012_r2 fix: 6.3.9600.23470
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23470
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26434
euvd windows_server_2016 fix: 10.0.14393.9612
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9612
euvd windows_server_2019 fix: 10.0.17763.9376
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9376
euvd windows_server_2022 fix: 10.0.20348.5761
euvd windows_server_2025 fix: 10.0.26100.33650
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33650

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 20 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is a heap-based buffer overflow (CWE-122) in Windows OLE DB, Microsoft's COM-based data access API that sits beneath many Windows and third-party data consumers (OLE DB providers, ADO, SQL tooling, Office data connectivity). When an OLE DB provider parses malformed attacker-supplied input - typically a crafted file opened by the user or a connection/data-source string pointing at an attacker-controlled endpoint - a heap buffer is written past its allocated boundary, corrupting adjacent heap metadata and enabling controlled memory corruption in the context of the calling process. Because OLE DB is a default Windows component present on Windows 10, Windows 11 (22H2, 23H2, 24H2, 25H2, 26H1, 26H2) and Windows Server 2012, 2012 R2, 2016, 2019, 2022 and 2025 (including Server Core installations), the vulnerable code path is reachable without any non-default configuration; the attacker-supplied data is the only prerequisite. Successful heap corruption in a privileged data-access context permits elevation of privilege to SYSTEM, consistent with the assessed vector's High confidentiality, integrity and availability impact while scope remains unchanged (S:U). Reliable exploitation of the specific heap layout was not confirmed as automatable by CISA SSVC (Automatable: no), and no public proof-of-concept was identified at time of analysis, though the technical impact if exploited is rated total.

Know when Windows gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (microsoft) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Network-delivered OLE DB data triggers the overflow but needs a victim action (UI:R), no prior auth (PR:N), low complexity, and heap corruption yields full code-execution impact (C/I/A:H).

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:19 cve.org
HIGH 8.8

DescriptionCVE.org

Heap-based buffer overflow in Windows OLE DB allows an unauthorized attacker to elevate privileges over a network.

Executive ViewAI

Why It Matters

A high-severity privilege escalation vulnerability in Windows OLE DB affects all supported Windows desktop and server versions, allowing an unauthenticated remote attacker who convinces a user to open a crafted file or connect to an attacker-controlled data source to gain SYSTEM-level control of the affected system. Although no public exploit identified at time of analysis and user interaction is required, the broad presence of affected Windows 10, 11, and Server installations means a single successful attack could lead to full compromise of critical machines. Leadership should prioritize patching to mitigate this risk, as the potential organizational impact is significant given the widespread deployment of affected systems.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.8%
Top 43% exploitable
Prevalence
Ubiquitous
Windows OLE DB ships in all supported Windows client and server editions
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.8%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

45
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +44
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.

CVE-2025-52691 CRITICAL POC
10.0 Dec 29

Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio

CVE-2019-0803 HIGH POC
7.8 Apr 09

Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in

CVE-2020-1472 MEDIUM POC
5.5 Aug 17

A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr

CVE-2025-33053 HIGH POC
8.8 Jun 10

Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables

CVE-2025-33073 HIGH POC
8.8 Jun 10

Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker

CVE-2025-13315 CRITICAL POC
9.3 Nov 19

Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b

CVE-2013-10047 CRITICAL POC
9.3 Aug 01

An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote

CVE-2012-10030 CRITICAL POC
9.3 Aug 05

FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit

CVE-2025-34101 CRITICAL POC
9.3 Jul 10

Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio

CVE-2025-13316 HIGH POC
8.2 Nov 19

Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred

CVE-2025-34095 CRITICAL POC
9.3 Jul 10

Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/

CVE-2025-11953 CRITICAL POC
9.8 Nov 03

React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy