Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain local user credentials
-
DeliveryAuthenticate to target Windows system
-
ExploitCraft malformed EFS API call
-
ExecutionTrigger heap-based buffer overflow in EFS component
-
PersistOverwrite heap metadata to hijack execution
-
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 | The attacker must have a valid local user account (PR:L - standard Windows user-level access is sufficient; no administrative privileges required). The attack is local (AV:L), meaning the attacker must be able to execute code on the target system - remote-only network access is insufficient without a separate initial access vector. No user interaction is required from any other account. The EFS component does not need to be actively encrypting files for the vulnerable code path to be reachable, as it is present in all affected Windows installations by default. Limiting factors: no remote unauthenticated path exists; exploitation is constrained to sessions or processes already running under a local account on the target machine. Organizations that strictly limit who can interactively log on or execute processes locally significantly reduce exposure. |
| Impact | CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately reflects a reliable local privilege escalation: low complexity, standard user account sufficient, no interaction required, full CIA impact after escalation to SYSTEM. No EPSS score or KEV listing is present in the input, meaning exploitation probability and confirmed in-the-wild activity are unknown from available data. The breadth of affected versions - 19 distinct Windows product lines - increases aggregate exposure significantly. No public exploit or POC is identified, which tempers immediate priority, but LPE vulnerabilities with AC:L/PR:L in Windows historically attract rapid weaponization once disclosed. The Microsoft MSRC reporter designation (secure@microsoft.com) is consistent with internal discovery, reducing the likelihood of pre-patch exploitation. Real-world risk is meaningful: any environment with multi-user Windows systems or where lateral movement from a low-privileged foothold is a concern should treat this as a prioritized patch - particularly Windows Server environments where EFS may be active. Missing: no EPSS score, no KEV, no confirmed POC; exploitation probability is inferred from CVSS complexity metrics alone. |
| Exploit ScenarioDerived | An attacker who has obtained a low-privileged local user account - via phishing, credential stuffing, or lateral movement - invokes a crafted EFS API call that triggers the heap-based buffer overflow in the EFS service, corrupting adjacent heap structures and redirecting execution to attacker-supplied shellcode running as SYSTEM. No public POC exists at time of analysis, but the low attack complexity (AC:L) suggests that once an exploit is developed it would be straightforward to execute reliably. In multi-user Windows Server environments, this class of LPE is particularly attractive for post-exploitation privilege escalation after initial compromise of a low-privileged service or user account. |
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 Encrypting File System (EFS) component enables a locally authenticated attacker to escalate privileges to SYSTEM level. The vulnerability spans virtually the entire modern Windows ecosystem - from Windows 10 1607 and Windows Server 2012 through Windows 11 26H1 and Windows Server 2025. No public exploit code or CISA KEV listing has been identified at time of analysis; vendor patch is available via MSRC.
RemediationAI
Apply the vendor-released security update from Microsoft, available through Windows Update, WSUS, or the Microsoft Update Catalog. The exact patched build targets are enumerated per product line above (e.g., Windows 11 24H2 → 10.0.26100.9445 or later; Windows Server 2025 → 10.0.26100.33438 or later). The authoritative fix reference is https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69841. If immediate patching is not feasible, compensating controls should focus on reducing attacker foothold: enforce application allowlisting to prevent execution of untrusted local binaries, restrict interactive local logon to only trusted administrative accounts, and monitor for unusual EFS API calls (e.g., via ETW or Sysmon event IDs related to EFS operations). Disabling EFS entirely (via Group Policy: Computer Configuration → Windows Settings → Security Settings → Public Key Policies → Encrypting File System) will mitigate the vulnerability surface if EFS is not operationally required, though this will prevent use of EFS-encrypted files. Note that Windows Server 2012 and 2012 R2 are beyond mainstream support; organizations running these versions should assess extended security update eligibility or migration priority.
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
The Encrypting File System (EFS) is a built-in Windows component that provides transparent filesystem-level encryption using symmetric keys protected by public-key cryptography. CWE-122 (Heap-based Buffer Overflow) indicates that EFS performs an out-of-bounds write into heap-allocated memory, likely during processing of EFS-related operations or RPC calls internal to the EFS service. Heap overflows in kernel-adjacent or privileged Windows services are a classic privilege escalation primitive: corrupting heap metadata or adjacent objects can redirect execution flow to attacker-controlled code running at elevated (SYSTEM) privilege. The CVSS vector AV:L/AC:L/PR:L/UI:N confirms the exploit is local, requires only a standard user account, and involves no user interaction - consistent with a crafted API or RPC call to an EFS endpoint exposed to low-privileged processes. Affected CPE data covers Windows 10 (1607, 1809, 21H2, 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1), and Windows Server 2012 through 2025.
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 access with low-privilege account sufficient; heap overflow in EFS yields SYSTEM execution, giving full CIA impact with no scope change.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Heap-based buffer overflow in Windows Encrypting File System (EFS) allows an authorized attacker to elevate privileges locally.
Executive ViewAI
Windows Encrypting File System vulnerability exposes millions of users across the enterprise to privilege escalation attacks. A locally authenticated attacker can gain SYSTEM-level access across Windows 10 through Windows 11 and all modern Server platforms, enabling potential compromise of encrypted data, critical infrastructure, and lateral movement to sensitive systems.
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-73590
GHSA-rvmq-h77h-wm99
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB