Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain physical access to device
-
ExploitSupply crafted input to Overlay Filter
-
ExecutionTrigger heap buffer overflow
-
ImpactExecute arbitrary code
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 PHYSICAL access to the target device (CVSS AV:P): the attacker must be able to physically interact with the machine to deliver input processed by the Windows Overlay Filter (WOF), the Windows component used for compressed/overlay file access. No authentication is required once physical access is obtained (PR:N) and no user interaction is needed (UI:N), and attack complexity is low (AC:L). The dominant limiting factor is the physical-access prerequisite, which prevents remote or scalable exploitation (SSVC Automatable: no) and confines realistic risk to physically exposed, shared, or unattended endpoints; the device must also run an unpatched affected build (e.g., Windows 11 24H2 <10.0.26100.9711 or Windows Server 2025 <10.0.26100.33650). |
| Impact | This is a high-CVSS component (C:H/I:H/A:H, total technical impact per SSVC) whose real-world priority is substantially blunted by the attack vector. The CVSS 3.1 vector CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H specifies a PHYSICAL attack vector (AV:P), meaning the attacker must have physical or near-physical access to the target device - not network or even local-logon access. All exploitation signals point AWAY from urgency: SSVC Exploitation status is 'none', Automatable is 'no' (consistent with a physical prerequisite that cannot be scripted at scale), and there is no KEV listing and no public exploit identified. EPSS is not provided in the input. The signals are internally consistent rather than conflicting: a serious memory-corruption impact gated behind a physical-access requirement. This is therefore a genuine code-execution flaw but a LOW-to-MODERATE real-world priority for most fleets - patch in normal cadence, with elevated priority only for physically exposed or shared-access devices (kiosks, lab machines, unattended endpoints). Note: although CVSS shows PR:N (no authentication), the physical vector effectively limits exposure to those who can touch the hardware. |
| Exploit ScenarioDerived | An attacker with physical access to an unlocked or accessible Windows device presents crafted input (e.g., attached storage or a locally supplied file) that is processed by the Windows Overlay Filter, triggering a heap-based buffer overflow and allowing arbitrary code execution. No public exploit code or active exploitation has been identified at time of analysis, and the low attack complexity (AC:L) means that once physical access is obtained, no special timing or conditions are needed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Code execution with full confidentiality, integrity and availability impact is achievable on unpatched Windows systems through a heap-based buffer overflow in the Windows Overlay Filter (WOF), but only for an attacker who already holds physical access to the target machine. The flaw carries a base score of 6.8 (CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H): physical access is required, yet once obtained no authentication and no user interaction are needed and attack complexity is low, so any unattended, shared or physically exposed endpoint that processes attacker-supplied input through WOF is at risk. No public exploit code has been identified at time of analysis and CISA's SSVC decision framework rates exploitation as none and automation as not feasible, but Microsoft has published a vendor fix and the technical impact is assessed as total, so the residual risk is concentrated in kiosks, lobby/plant-floor PCs, and other hands-on devices rather than in remotely reachable server fleets.
RemediationAI
Vendor-released patch: Microsoft has published a fix for CVE-2026-69958 through the Microsoft Security Response Center (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69958); apply the current cumulative update for each affected build so that it reaches or exceeds the EUVD-listed remediated thresholds - for example Windows 11 24H2 / Windows Server 2025 at 10.0.26100.9711 and 10.0.26100.33650 respectively, Windows 11 23H2 at 10.0.22631.7652, Windows 11 25H2 at 10.0.26200.9711, Windows 11 26H1 at 10.0.28000.3231, Windows 11 26H2 at 10.0.26300.9711, Windows 10 21H2/22H2 at 10.0.19044.7807, Windows 10 1607 / Server 2016 at 10.0.14393.9612, Windows 10 1809 / Server 2019 at 10.0.17763.9376, Server 2022 at 10.0.20348.5761, Server 2012 at 6.2.9200.26434 and Server 2012 R2 at 6.3.9600.23470 - and confirm the exact KB number against the MSRC advisory before deployment, since these EUVD values are build thresholds rather than KB identifiers. Because exploitation depends entirely on an attacker obtaining hands-on access, the highest-value compensating controls are physical and platform lockdown rather than network filtering: enforce BitLocker/device encryption with pre-boot PIN or TPM+PIN so offline tampering with overlay/compressed data cannot be staged, require UEFI passwords and Secure Boot, deploy kiosk/assigned-access or shell-launcher modes plus a screen lock timeout on publicly reachable endpoints, and disable or physically block unused USB and removable-media ports (trade-off: breaks legitimate peripheral use and imaging workflows). Do not attempt to disable the Windows Overlay Filter driver as a mitigation on CompactOS, WIMBoot or system-compressed deployments, since WOF-compressed system files would become unreadable and the host may fail to boot; on non-compressed systems, avoiding overlay/compressed file usage reduces exposure but does not eliminate the defect. Until patching is complete, prioritize update and physical-exposure review for shared workstations, point-of-sale/kiosk terminals, lab and plant-floor machines, and any Server Core or legacy Server 2012/2012 R2 systems that are still receiving updates. No public exploit code has been identified at time of analysis, so emergency out-of-band action is warranted only for endpoints that are physically accessible to untrusted people.
Affected VersionsENISA
Affected Packages
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 Windows Overlay Filter (WOF) is the Windows component (wof.sys / WOF driver plus its user-mode support) that implements file-level overlay compression, underpinning features such as CompactOS, WIMBoot and system-file compression; it decompresses and maps overlay/compressed file data on the fly, including data on mounted volumes and offline images. The vulnerability is a CWE-122 heap-based buffer overflow: memory is allocated on the heap using one computed size while a length or bounds check on externally influenced data is missing or incorrect, so a crafted input causes writes past the end of the allocation, corrupting adjacent heap metadata and objects. That primitive is what enables the assessed high impact to data confidentiality, integrity and availability (C:H/I:H/A:H, total technical impact per SSVC), because corruption of the process/driver heap can be shaped into controlled execution in the context of the affected component. The narrow AV:P vector reflects the delivery constraint rather than a weakness in the memory-safety defect itself: the attacker must be able to physically interact with the device so that its input is processed by WOF, which is why the SSVC Automatable flag is 'no' and why the same code defect would be far more severe if it were reachable over the network. Affected builds span Windows 10, Windows 11 and Windows Server from 2012 through 2025, as enumerated in the EUVD version ranges, indicating the flaw sits in a long-lived shared code path rather than in a recent feature addition.
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:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Physical access is required so AV:P; no authentication or interaction needed (PR:N/UI:N) with low complexity, and memory corruption yields full code execution (C/I/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Heap-based buffer overflow in Windows Overlay Filter allows an unauthorized attacker to execute code with a physical attack.
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-99116
GHSA-w9xr-hcr8-3chc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB