Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-105004 Overview
CVE-2026-105004 is an out-of-bounds read vulnerability [CWE-125] in the Windows Overlay Filter (wof.sys) driver. An authorized local attacker can exploit this flaw to elevate privileges on an affected Windows system. The Windows Overlay Filter is a file-system filter driver used to support compact OS and container file virtualization scenarios.
Microsoft published the advisory on October 13, 2026. The vulnerability requires local access and low privileges, with no user interaction needed. Successful exploitation grants an attacker SYSTEM-level privileges, enabling full compromise of confidentiality, integrity, and availability on the host.
Critical Impact
A local, authenticated attacker can read out-of-bounds kernel memory in the Windows Overlay Filter driver to escalate privileges to SYSTEM.
Affected Products
- Microsoft Windows (Windows Overlay Filter component)
- Refer to the Microsoft Security Update CVE-2026-105004 advisory for the authoritative product and build list
- Specific affected builds are not enumerated in the NVD record
Discovery Timeline
- 2026-10-13 - CVE CVE-2026-105004 published to NVD
- 2026-10-13 - Last updated in NVD database
Technical Details for CVE-2026-105004
Vulnerability Analysis
The vulnerability resides in the Windows Overlay Filter, a kernel-mode file-system filter driver that supports WIM-backed and compact OS file virtualization. An out-of-bounds read occurs when the driver processes attacker-influenced input without properly validating buffer boundaries. The driver reads memory beyond the intended object, exposing adjacent kernel data to the caller.
Because the component runs in kernel space, the leaked data can include pointers, tokens, or structure fields that an attacker uses to defeat kernel address space layout randomization (KASLR) and build a reliable local privilege escalation chain. Exploitation requires an existing low-privileged account on the target system.
Successful exploitation yields SYSTEM privileges, allowing installation of persistent malware, credential theft from LSASS, disabling of security tooling, and lateral movement using harvested credentials.
Root Cause
The root cause is missing or incorrect bounds checking on a buffer read inside the Windows Overlay Filter driver [CWE-125]. The driver trusts a length or offset value controlled by the calling process when accessing a structure in memory. Microsoft has not published the vulnerable function name or structure details in the public advisory.
Attack Vector
The attack vector is local. An authenticated user issues crafted I/O control requests (IOCTL) or triggers filter callbacks against the Windows Overlay Filter driver from user mode. The malformed request causes the driver to read past the end of a kernel buffer, returning privileged data to the attacker-controlled process.
Since no exploit code or proof of concept is publicly available at this time, defenders should treat the technical details above as a generalized model of OOB-read kernel escalation flaws. See the Microsoft Security Update CVE-2026-105004 advisory for authoritative technical details.
Detection Methods for CVE-2026-105004
Indicators of Compromise
- No public indicators of compromise have been published for CVE-2026-105004 at the time of writing.
- Unexpected processes spawning as NT AUTHORITY\SYSTEM from a user session are a general indicator of local privilege escalation.
- Loading or interaction with wof.sys by non-system binaries in user context warrants review.
Detection Strategies
- Hunt for processes started by standard users that subsequently execute child processes under SYSTEM context.
- Monitor for unusual DeviceIoControl calls or handle opens targeting the Windows Overlay Filter device object from unprivileged processes.
- Correlate kernel crash events (BugCheck, Event ID 1001) involving wof.sys with user-session activity, which may indicate failed exploitation attempts.
Monitoring Recommendations
- Enable Windows Defender Application Control or AppLocker to restrict execution of unknown binaries that could serve as exploit stagers.
- Centralize Sysmon and Windows Security logs in a SIEM to detect privilege transitions and anomalous driver interactions.
- Track installation of patches tied to the October 2026 Microsoft security update across the fleet to verify remediation coverage.
How to Mitigate CVE-2026-105004
Immediate Actions Required
- Apply the Microsoft security update referenced in the Microsoft Security Update CVE-2026-105004 advisory to all affected Windows systems.
- Prioritize patching of multi-user systems, terminal servers, and developer workstations where untrusted local code may run.
- Audit local account inventories and remove unused or stale accounts that could be leveraged by an attacker with initial foothold.
Patch Information
Microsoft released a security update addressing CVE-2026-105004 on October 13, 2026. Administrators should deploy the update through Windows Update, Windows Server Update Services (WSUS), or Microsoft Intune. Consult the Microsoft Security Update CVE-2026-105004 advisory for the specific KB article and build numbers that correspond to each supported Windows version.
Workarounds
- No official vendor workaround is documented. Patching is the required remediation.
- Enforce the principle of least privilege and restrict interactive logon rights to reduce the pool of accounts able to trigger the flaw.
- Deploy endpoint protection capable of detecting local privilege escalation behavior and kernel-driver abuse until patches are applied.
# Verify installed updates on Windows (PowerShell)
Get-HotFix | Sort-Object -Property InstalledOn -Descending | Select-Object -First 20
# Trigger WSUS/Windows Update scan and install
UsoClient StartScan
UsoClient StartDownload
UsoClient StartInstall
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

