WinFsp Vulnerability CVE-2026-3006 Allows Local Attackers to Escalate Privileges to SYSTEM via Race Condition in Kernel Driver
A seemingly minor flaw in WinFsp can grant a local attacker complete control over a Windows computer by escalating privileges all the way to the SYSTEM account. The platform, widely used to mount virtual disks, network storage, and non-standard file systems, contains components that run with high privileges inside the Windows kernel. Researchers found that these components can be abused through a race condition, turning an ordinary user or compromised process into a full system owner.
Technical Details of CVE-2026-3006
The vulnerability, assigned identifier CVE-2026-3006 and rated 7.0 on the CVSS 3.1 scale, impacts WinFsp 2.1.25156 and all prior versions. It stems from a classic time-of-check-to-time-of-use race condition: when multiple operations access the same resource simultaneously, the driver may process them in an unexpected order. An attacker who times the operations correctly can trigger a memory overflow inside the kernel driver, corrupting a controllable memory region and ultimately executing arbitrary code with SYSTEM rights.
Because the flaw resides in kernel-mode code, the consequences are severe. After gaining SYSTEM privileges the attacker can alter protected system files, install new services and drivers, disable security products, read any local data, and create additional accounts with administrative rights.
Attack Requirements and Scope
The vulnerability cannot be exploited remotely. An attacker must first obtain local execution capability—by running a malicious program, using a compromised user account, or gaining an initial foothold through another vector. Once local access is achieved, the race condition can be triggered to elevate privileges.
The risk extends far beyond users who install WinFsp manually. Many third-party applications that provide file-system virtualization or cloud storage integration ship vulnerable versions of the WinFsp driver. Administrators are therefore advised to audit both standalone WinFsp installations and any bundled copies present on their systems.
Remediation and Recommendations
Developers have already addressed the issue in WinFsp 2.2B1. The Cyber Security Agency of Singapore urges organizations to deploy the updated version immediately. Additional defensive measures include limiting the number of users with local administrative rights and continuously monitoring for unexpected driver or service installations as well as suspicious processes related to WinFsp.
The flaw was discovered by security researcher Tai Kiat Lung. Organizations that rely on WinFsp or any software that depends on it should treat the update as a high priority to prevent local attackers from converting limited access into full system ownership.
Related articles
Browser Built on Mistakes: How Real-World Attacks Shaped Modern Browser Defenses
Browser security features such as process isolation, sandboxing, and restrictions on code execution were not designed in isolation but evolved directly in response to concrete attacks over more than a decade. Early threats like malicious Flash advertisements in 2015 demonstrated how a single compromised banner could compromise an entire system, prompting the industry to phase out plugins entirely. Later discoveries, including the Spectre vulnerability, forced browsers to implement stricter site isolation and timing-attack mitigations that remain in place today. Session hijacking and malicious browser extensions further drove the adoption of stronger cookie protections and permission models. BI.ZONE analysts trace this history through specific incidents to show why current architectures prioritize separation of sites into distinct processes. The resulting design reduces the blast radius of any single exploit and continues to adapt as new attack classes emerge.
cKEV Index Launches to Prioritize Vulnerabilities as AI Accelerates Exploit Development
CyberOK has introduced the open cKEV Index, a catalog of high-priority vulnerabilities ranked by the Urgent Patch Score (UPS) methodology. The index incorporates timelines of events such as exploit publication, proof-of-concept releases, and confirmed attacks to help organizations prioritize patching under resource constraints. It addresses the growing gap between rapid AI-assisted vulnerability discovery and slower remediation processes at both vendors and customers. Examples from Anthropic reports highlight how threat actors used AI agents for reconnaissance, code analysis, and exploit development against Android apps and web applications. Microsoft and Oracle have publicly linked increased vulnerability findings and larger patch releases to AI tooling. The UPS framework defines progressive phases from Radar to Emergency/IR, allowing teams to act on strong signals without waiting for full confirmation. An open version of the catalog is now available with detailed event histories for Urgent Patch and Emergency stages.
Apache HTTP Server 2.4.69 Patches 20 Vulnerabilities Including CVSS 9.8 Issues
The Apache HTTP Server development team released version 2.4.69 on October 1, 2026, addressing a total of 20 vulnerabilities. While the Apache Security Team assessed most issues as moderate or low in impact, several vulnerabilities received CVSS base scores as high as 9.8. The update includes fixes for stack-based buffer overflows, use-after-free conditions, and out-of-bounds writes affecting multiple modules. No vulnerabilities were rated Critical or Important by the developers, with five classified as Moderate and fifteen as Low. Specific fixes cover the mod_vhost_alias, mod_http2, mod_dav, and mod_dav_fs modules, along with Windows-specific path handling problems.
BrokenPipe PoC Exploits Steam Client Service for Silent SYSTEM Privilege Escalation on Windows
A new proof-of-concept named BrokenPipe demonstrates how a standard Windows user can escalate privileges to NT AUTHORITY\SYSTEM through the Steam Client Service without requiring administrator credentials or triggering a UAC prompt. The vulnerability stems from insufficient signature validation in VDF installation scripts processed by steamservice.exe, allowing an attacker to control the execution path of a malicious script. The issue affects Steam version 10.96.30.42 on both Windows 10 and Windows 11, though no public CVE has been assigned yet. Valve was notified of the flaw in March, several months prior to public disclosure. The attack is strictly local and requires initial code execution under a standard user account, making it relevant for shared or corporate environments. Security teams are advised to inventory Steam installations, apply application allowlisting, and monitor for anomalous SYSTEM-level processes linked to the service while awaiting an official patch.