Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local session
-
DeliveryCraft malformed DFS request
-
ExploitTrigger heap-based buffer overflow in DFS component
-
ExecutionCorrupt heap metadata or function pointer
-
ImpactExecute arbitrary code 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 an authenticated local session on the target Windows machine - the attacker must have the ability to execute code as a low-privileged user (PR:L). No special non-default configuration of DFS is described as necessary; the DFS client and server components are present by default across all affected Windows versions. No user interaction (UI:N) beyond the attacker's own actions is required. The local attack vector (AV:L) means remote-only network access is insufficient - the attacker must have a local or terminal-server session, or must chain this flaw after a remote initial-access vector. Exploitation is constrained to physical or virtual machine access (including RDP/interactive logon), meaning network-perimeter controls alone do not prevent post-exploitation use of this vulnerability. |
| Impact | The CVSS 7.8 (High) rating with vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H accurately reflects a local privilege escalation with low attack complexity and no user interaction required once the attacker has a local foothold. The low-complexity, no-UI-interaction profile means that once an attacker holds any user-level local session - via phishing, a compromised service account, or RDP access - they can chain this DFS flaw to gain full system control. No EPSS data is present in the input, no CISA KEV listing is confirmed, and no public exploit code has been identified, which somewhat tempers urgency compared to actively exploited LPE flaws. However, the combination of AC:L, PR:L, and full C:H/I:H/A:H impact makes this a strong post-exploitation primitive, and its presence across virtually all supported Windows versions significantly increases the attack surface. Even organizations running fully patched workstations on recent Windows 11 builds remain exposed until the specific patch levels listed in the EUVD advisory are applied. The breadth of the affected version matrix - 19 distinct product lines - indicates this is a systemic issue in a shared DFS code path rather than a version-specific regression, warranting organization-wide patch deployment as a priority. |
| Exploit ScenarioDerived | An attacker who has obtained a low-privileged local session on a Windows endpoint - for example, through a phishing-delivered initial access or a compromised service account - sends a crafted request to the Windows DFS component that triggers the heap overflow. The corrupted heap memory allows the attacker to redirect execution into shellcode or an existing gadget chain, yielding SYSTEM-level privileges. No public proof-of-concept code has been identified at time of analysis, but the low complexity of exploitation (AC:L) suggests this class of LPE is feasible for skilled adversaries. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 09, 2026
Heap-based buffer overflow in the Windows Distributed File System (DFS) component allows a locally authenticated attacker to escalate privileges to SYSTEM-level access on affected Windows clients and servers. The vulnerability spans an exceptionally broad range of Microsoft Windows releases, from Windows 10 version 1607 and Windows Server 2012 through the most current Windows 11 26H1 and Windows Server 2025 builds. No public exploit code or CISA KEV listing has been identified at time of analysis, and Microsoft has released patches for all affected versions.
RemediationAI
Apply the Microsoft-released patches via Windows Update or WSUS to bring each product line to or above the fixed build numbers: Windows 11 24H2 to 10.0.26100.9445, Windows 11 25H2 to 10.0.26200.9445, Windows 11 26H1 to 10.0.28000.2954, Windows 11 23H2 to 10.0.22631.7582, Windows 10 22H2 to 10.0.19045.7725, Windows 10 21H2 to 10.0.19044.7725, Windows 10 1607 and Server 2016 to 10.0.14393.9512, Windows 10 1809 and Server 2019 to 10.0.17763.9245, Server 2022 to 10.0.20348.5622, Server 2025 to 10.0.26100.33438, Server 2012 R2 to 6.3.9600.23397, and Server 2012 to 6.2.9200.26349. The full patch details are published at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69424. If immediate patching is not possible, consider restricting local interactive and remote desktop access to sensitive servers, and auditing which accounts hold local logon rights - this reduces the pool of identities that could supply the required PR:L prerequisite. Note that disabling DFS entirely may disrupt file-share namespace functionality in Active Directory environments and should be evaluated carefully against business dependencies before deployment as a workaround.
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
Windows DFS (Distributed File System) is a built-in Windows networking subsystem that aggregates file shares across multiple servers into a single logical namespace, used heavily in enterprise Active Directory environments. CWE-122 (Heap-based Buffer Overflow) indicates the overflow occurs in dynamically allocated heap memory within the DFS driver or client component - a classic memory-corruption class that allows an attacker to corrupt adjacent heap objects, overwrite function pointers, or hijack control flow. Exploiting such flaws in a Windows kernel-mode or privileged user-mode component typically yields SYSTEM-level code execution. The affected products span CPE ranges including Windows 10 (10.0.14393 through 10.0.19045), Windows 11 (10.0.22631 through 10.0.28000), and Windows Server 2012 (6.2.9200) through Server 2025 (10.0.26100), indicating the vulnerable code path has been present in the Windows codebase for well over a decade.
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 session required for DFS access; low complexity once authenticated; full C/I/A impact consistent with SYSTEM-level privilege escalation via kernel/privileged component overflow.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Heap-based buffer overflow in Windows Distributed File System (DFS) allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A Windows Distributed File System vulnerability enables local users to gain complete system-level control, affecting organizations across Windows 10, Windows 11, and Windows Server deployments. This broad impact across enterprise and desktop operating systems creates significant privilege escalation risk for insider threats and compromised accounts; no public exploit has been identified at time of analysis. Immediate patching across all Windows systems is critical to prevent attackers from leveraging local access into full system compromise.
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-73493
GHSA-j2xp-jw6w-vj4c
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB