Windows Filtering Platform EUVD-2026-29575

Exploitation requires an attacker to already possess local, authenticated access to the target Windows system with at minimum standard user (low) privilege - as confirmed by CVSS PR:L. The attack vector is strictly local (AV:L), meaning remote unauthenticated exploitation is not possible. No special non-default configuration is required, but the attacker must have the ability to execute arbitrary code on the system; this limits exposure to scenarios where initial compromise has already occurred (e.g., via malware, stolen credentials, or an insider threat). What limits exploitation: the requirement for local code execution eliminates the vast majority of opportunistic, remote-first attack scenarios; the scope is unchanged (S:U), meaning the attacker cannot break out to affect the hypervisor or adjacent systems; and impact is partial (C:L, I:L) with no availability impact (A:N), capping the immediate damage from WFP bypass alone.

The CVSS base score of 4.4 (Medium) is consistent with the realistic threat model: local access and low-privilege authentication are prerequisites, limiting the attacker pool to users who already have a foothold on the target system. The CVSS attack complexity is low (AC:L), meaning exploitation does not rely on race conditions or non-default configuration once local access exists, which is a mild amplifier. However, EPSS at 0.04% places this in the bottom 11% of exploitability across all CVEs - suggesting the security community and threat actors alike assess active exploitation as unlikely in the near term. SSVC parameters reinforce this: exploitation status is 'none', the attack is not automatable (no remote vector), and technical impact is only 'partial'. This vulnerability is not in the CISA KEV catalog and no POC code has been identified. The primary real-world concern is local privilege escalation chains where WFP bypass serves as a stepping stone - for example, bypassing host firewall rules to enable lateral movement after initial compromise. Organizations with strict host firewall policies or endpoint detection relying on WFP-based drivers should treat this as a meaningful patch priority even though raw CVSS and EPSS are moderate.

An attacker who has already gained a low-privileged interactive or remote shell session on a target Windows host - for example, via a phishing payload or compromised service account - executes local code that abuses the WFP access control flaw to bypass the host-based firewall or network filtering policy. This bypass could allow the attacker to establish outbound connections to a command-and-control server on a port or protocol otherwise blocked by WFP rules, facilitating lateral movement or data exfiltration that the security feature was designed to prevent. No public exploit or POC code has been identified at time of analysis, so exploitation currently requires attacker-developed tooling.