Windows UDFS EUVD-2026-100368

Exploitation requires the attacker to already hold authenticated, low-privileged local code execution on the target (PR:L, AV:L) - this is a post-access privilege-escalation bug, not a remote entry point. The attacker must then cause the Windows UDFS (Universal Disk Format) file system driver to parse an attacker-controlled UDF volume, such as a malicious ISO, optical disc, or USB/removable image that is mounted or opened; the overflow is in the driver's parsing of that structure. Limiting factors: no remote network vector, no capability for a fully unauthenticated attacker, and the need to deliver and have the malformed UDF volume processed by the driver. No user interaction is required once the volume is presented (UI:N), and attack complexity is low (AC:L).

This is a credible operational priority but not an emergency. The provided CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) describes a local privilege-escalation flaw: an attacker must already have the ability to execute code on the host as an authenticated low-privileged user (PR:L), after which low attack complexity (AC:L) and no user interaction (UI:N) make the exploit reliable, yielding full confidentiality, integrity and availability impact (C:H/I:H/A:H) - consistent with kernel-mode code execution via a vulnerable file system driver. No EPSS score was supplied, so exploitation probability cannot be quantified from this data. The CVE is NOT listed in CISA KEV and no public POC is referenced, so there is no public exploit identified at time of analysis. The signals are therefore internally consistent (all point to a serious-but-local EoP) rather than conflicting; the main caveat is that heap-overflow driver bugs are high-value second-stage exploits for sandbox escapes and post-compromise escalation, so despite the local-only vector it should be patched on Patch Tuesday cadence, prioritized on multi-user and endpoint systems where untrusted code or removable media (UDF/optical/ISO) is mounted.

An attacker who already has low-privileged code execution on a Windows host (e.g., via phishing or a compromised standard user account) crafts a malformed UDF file system structure - for instance on a malicious ISO or optical/USB image - and triggers the Windows UDFS driver to parse it, overflowing a heap buffer. By grooming the kernel pool and corrupting adjacent structures, the attacker executes code in kernel context and elevates to SYSTEM. No public POC is referenced, and the low attack complexity (AC:L) means a working exploit would be reliable once developed.