Windows Client for NFS EUVD-2026-99664

Exploitation requires (1) the optional 'Client for NFS' feature/role to be present on the target Windows system - it is not installed by default on client or server SKUs - and (2) an attacker who already holds authenticated low-privileged local access to that host (PR:L, AV:L). No user interaction is needed (UI:N). The scope is unchanged (S:U), so impact is confined to the local system. Principal limiting factors for defenders: the attack cannot be performed remotely, it cannot run as a fully unauthenticated actor, and hosts without the NFS client feature enabled are not exposed - which meaningfully narrows the real-world attack surface despite the high technical impact.

This is a credible but second-tier priority - a genuine local privilege-escalation flaw rather than a remotely-wormable crisis. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N) is internally consistent with the description's 'authorized attacker ... elevate privileges locally': an attacker needs an existing low-privileged foothold on the Windows host, there is no network vector, and no user interaction is required. All three signals pointing toward lower urgency agree: CISA's SSVC decision framework lists Exploitation as 'none' (no observed or public exploitation), Automatable as 'no' (consistent with a local-only EoP that cannot be sprayed at scale), and there is no CISA KEV listing and no public POC. The one signal pulling the other way is SSVC Technical Impact = 'total', which aligns with the C:H/I:H/A:H impact metrics - once triggered, the overflow yields full compromise of the local system (typically SYSTEM). No EPSS score was provided in the input, so probabilistic exploitation likelihood cannot be quantified here. Net: high technical impact but low current exploitation signal and a local-only, authentication-gated vector make this a patch-in-normal-cycle item that rises in priority on multi-user hosts, terminal servers, and any environment where limited-privilege users must be contained.

A low-privileged but authenticated user (or malware already running in a limited user context) on a Windows system that has the Client for NFS feature present interacts with the NFS client in a way that triggers the heap-based buffer overflow, corrupting heap memory to hijack execution and elevate to SYSTEM. No public exploit code has been identified at time of analysis, and exploitation requires prior local access, so this is most relevant as a post-compromise escalation step rather than an initial-access vector.