Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconObtain low-privilege local user session
-
DeliveryCraft malformed DCOM activation or marshaling request
-
ExploitSubmit request to SYSTEM-privileged DCOM Server process
-
InstallTrigger heap-based buffer overflow
-
C2Corrupt heap control structures or function pointers
-
ExecuteRedirect DCOM Server execution
-
ImpactAchieve arbitrary code execution as SYSTEM
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 a locally authenticated session with at least low privileges on the target system (PR:L per CVSS vector). Any standard Windows user account is sufficient - no administrative rights are needed to submit DCOM requests to the server process. DCOM Server is enabled and runs by default on all supported Windows installations; no special feature, non-default configuration, or specific deployment mode is required to expose the vulnerable code path. Exploitation is strictly local (AV:L): an attacker cannot reach this vulnerability directly over the network without first obtaining local code execution on the host (e.g., via an initial-access exploit, VPN session, or RDP access). Scope is unchanged (S:U) - the overflow does not directly pivot to other systems, but achieving SYSTEM on the local host provides a strong basis for lateral movement and credential harvesting. |
| Impact | CVSS 3.1 rates this 7.8 (High) with AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. The local attack vector (AV:L) bounds the direct exposure - remote exploitation is not directly possible - but PR:L confirms that any standard authenticated local session is sufficient, removing the most common practical barrier to LPE exploitation. AC:L and UI:N together indicate that no special race conditions, user actions, or non-default configurations are required once local access is established. No EPSS data was provided in the available intelligence; the absence of both a public exploit and a CISA KEV listing reduces immediate triage urgency relative to actively exploited issues. However, the extraordinary breadth of affected versions - including end-of-life Windows Server 2012 and 2012 R2 where patching requires Extended Security Updates - means the aggregate unpatched surface will remain large for an extended period. The heap overflow target is a universally running, highly privileged Windows service; any organization treating this as a low-priority patch risks leaving a reliable privilege escalation primitive open to any attacker who achieves initial foothold. |
| Exploit ScenarioDerived | An attacker who has gained a standard user session on a Windows host - for example, through credential phishing or exploitation of a network-exposed initial-access vulnerability - submits a crafted DCOM activation or interface-marshaling request to the locally running DCOM Server process. The malformed request triggers a heap buffer overflow (CWE-122), corrupting heap metadata or overwriting a function pointer within the SYSTEM-privileged process, enabling the attacker to redirect execution and obtain SYSTEM-level code execution. No public exploit code has been identified at time of analysis, but AC:L and UI:N indicate that weaponization from an established low-privilege foothold would be technically straightforward. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 08, 2026
Heap-based buffer overflow in Windows DCOM Server enables a locally authenticated, low-privilege attacker to escalate to SYSTEM-level on affected hosts via a malformed DCOM activation or marshaling request. The vulnerability (CWE-122) spans effectively the entire active Microsoft Windows ecosystem - from end-of-life Server 2012 through current Windows 11 26H1 and Server 2025 - amplifying aggregate exposure significantly. No public exploit code and no CISA KEV listing have been identified at time of analysis; however, the low attack complexity and absence of user interaction requirements make this a practical post-initial-access privilege escalation primitive.
RemediationAI
Apply the Microsoft security update distributed through Windows Update, WSUS, or Microsoft Update Catalog; consult the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69284 for the specific KB article per affected product. Target build numbers per platform are provided in the EUVD-affected version data (e.g., Windows Server 2025 to ≥10.0.26100.33438, Windows Server 2022 to ≥10.0.20348.5622, Windows 10 21H2/22H2 to ≥10.0.19044.7725/10.0.19045.7725). Windows Server 2012 and 2012 R2 are end-of-life; organizations still operating these must procure Extended Security Update (ESU) entitlements to receive the patch. If immediate patching is not feasible, enforce the principle of least privilege by removing unnecessary local accounts, restricting interactive logon rights for service accounts via Group Policy (User Rights Assignment), and deploying Windows Firewall rules to limit local inter-process DCOM traffic - noting these are mitigations only and do not eliminate the vulnerability.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 19 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
DCOM (Distributed Component Object Model) extends Microsoft's COM framework to support inter-process and networked component activation; the DCOM Server process (hosted in services such as DcomLaunch/RPCSS) runs with SYSTEM-level privileges and handles local marshaling requests from any authenticated session. CWE-122 (Heap-based Buffer Overflow) indicates an out-of-bounds write into heap memory within this privileged process, likely triggered by a crafted object activation or interface-pointer marshaling payload. Because the DCOM Server operates with elevated privileges, a successful heap corruption primitive yields privilege escalation from any low-privilege context to SYSTEM. Affected CPE ranges cover Windows 10 (versions 1607 through 22H2), Windows 11 (23H2 through 26H1), Windows Server 2012/R2, 2016, 2019, 2022, and 2025 - including both full and Server Core installations.
Know when Windows 10 1607 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
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local-only exploitation requiring only a low-privilege session; full system impact post-overflow but no scope change across machine boundaries.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Heap-based buffer overflow in Windows DCOM Server allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A heap buffer overflow in Windows DCOM affects all supported Microsoft Windows systems from Server 2012 through Windows 11 and Server 2025, allowing authenticated users with low privileges to escalate to SYSTEM-level access. This privilege escalation vulnerability creates substantial risk across enterprises, as compromised local accounts can gain administrative control without user interaction, enabling lateral movement and data theft. Immediate assessment and patching is critical to contain post-compromise escalation risks within corporate environments.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
More in Windows 10 1607
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
EUVD-2026-73432
GHSA-2m58-vm8w-cpww
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB