Windows NTFS EUVD-2026-73460

Exploitation requires a low-privileged network account on the target system (PR:L per the CVSS vector - at minimum, a domain user or equivalent SMB-authenticated session) and some form of user interaction (UI:R), which likely involves a victim user or process accessing an attacker-controlled or crafted NTFS resource such as a network share or mounted volume. Fully unauthenticated remote exploitation is not possible given PR:L. The vulnerability is scoped to Windows systems running the affected NTFS driver builds across Windows 10, 11, and Server 2012-2025 product lines. Network-based triggering (AV:N) is consistent with NTFS driver exposure via SMB, but this does not eliminate the possibility of local triggering via crafted filesystem images. The required user interaction limits fully automated mass-exploitation scenarios.

The CVSS 8.0 vector (AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H) accurately reflects the threat profile: network-accessible, low complexity, low-privileged attacker, with some required user interaction, yielding full CIA impact. The UI:R requirement provides some friction against fully automated, opportunistic exploitation, reducing the likelihood of wormable or mass-scanning attack chains. EPSS data is not provided in the input, and the vulnerability is not listed in CISA KEV - but the absence of current exploitation evidence does not diminish patch urgency given historical patterns for Windows kernel filesystem bugs with network vectors, which have attracted rapid weaponization after patch release via patch-diffing. The scope of affected versions - spanning over a decade of Windows Server releases and all consumer Windows 10/11 branches - means even a mid-sized municipal IT team in boleslawiec should treat this as an urgent patch priority, particularly for any systems exposing SMB to internal or semi-trusted networks. The C:H/I:H/A:H impact metrics are consistent with a privilege escalation chain that terminates at SYSTEM level, not merely information disclosure.

A low-privileged domain user authenticates to a target Windows system over SMB and induces a victim process (or the user themselves) to access a crafted NTFS structure - such as a malicious file share or specially formatted volume - triggering an out-of-bounds read in the kernel NTFS driver that leaks kernel memory layout. The attacker uses the leaked addresses to bypass ASLR and chains a secondary write primitive to overwrite a security token or function pointer, escalating from low-privileged user to SYSTEM. No public exploit code has been confirmed, but the patch-diff surface for widely distributed Windows updates is well-understood by exploit developers.