Windows Bind Filter Driver EUVD-2026-73118

Exploitation requires an authenticated session on the target system with at least a standard (low-privileged) user account - confirmed by CVSS PR:L. The attacker must execute code locally on the affected machine, ruling out fully remote, unauthenticated exploitation. High attack complexity (AC:H) indicates that exploitation likely requires a race condition or specific heap-layout manipulation, reducing reliability and making automated mass exploitation harder. Exploitation is limited to Windows 11 (23H2, 24H2, 25H2, 26H1) and Windows Server 2025 - older Windows versions (10, Server 2019/2022) are not listed as affected. The Bind Filter Driver is a default system component; no special feature configuration is required to expose the vulnerability beyond having a user-accessible session.

The CVSS 3.1 base score of 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately reflects the realistic exploitation posture: local access with a standard user account is required, and the high attack complexity constrains opportunistic mass exploitation. Full C/I/A impact reflects the post-exploitation SYSTEM-level access achievable. No CISA KEV listing is present, and no public POC is referenced in the available intelligence, consistent with the 7.0 score rather than an emergency-tier critical. EPSS data is not provided; however, kernel UAF privilege escalation flaws in Windows historically attract exploit development within weeks of patch release, particularly when affecting broad OS version ranges. The scope of affected builds (five Windows 11 versions plus two Windows Server 2025 variants) indicates wide exposure within enterprise and consumer Windows environments. The primary risk is insider threat or post-initial-access lateral movement - an attacker already holding a standard user session can leverage this to gain SYSTEM before detection. This should be prioritized in standard Patch Tuesday patch cycles.

An attacker who has already obtained a standard (non-admin) user session on a Windows 11 or Windows Server 2025 host - via phishing, credential theft, or initial access - runs a crafted local binary that triggers a race condition in the Bind Filter Driver's memory management, causing a use-after-free in kernel space. By controlling the freed memory region, the attacker redirects kernel execution to overwrite a security token, elevating the process to SYSTEM. From SYSTEM, the attacker can disable endpoint controls, dump credentials from LSASS, or establish persistence. No public POC is known at time of analysis.