Windows DNS Server EUVD-2026-73342

The Windows DNS Server role must be installed and running on the target host - this is not a default Windows installation but is extremely common in Active Directory-joined environments. The DNS service port (UDP/TCP 53) must be reachable by the attacker, either from the internet or from within the local network. Exploitation requires winning a race condition (CVSS AC:H), meaning the attacker must send concurrent crafted requests with precise timing, which limits reliable one-shot exploitation but does not prevent determined attackers from succeeding through repeated attempts. No authentication is required (PR:N). No special DNS zone configuration or feature enablement beyond the DNS Server role itself is indicated as a prerequisite.

The CVSS 8.1 score (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) captures the core tension: all three impact components are High - a successful exploit means full system compromise - but AC:H reflects the inherent difficulty of reliably winning a race condition over a network. Real-world exploitation requires the attacker to win a timing race against concurrent server threads, which is harder to automate reliably than a straightforward buffer overflow but not impossible with repeated attempts. EPSS data is not available in the input to further calibrate probability. No KEV listing means CISA has not confirmed active exploitation, and no POC has been identified in the provided data. Despite AC:H, DNS Servers are typically internet- or intranet-facing and process high request volumes, which can increase the statistical window for race exploitation. Organizations with externally-facing Windows DNS infrastructure face the greatest exposure.

An unauthenticated attacker sends a high volume of carefully timed, concurrent DNS queries to a vulnerable Windows DNS Server, targeting the unsynchronized shared resource to win the race condition. After repeated attempts to reliably hit the timing window, the attacker achieves memory corruption in the DNS Server process, leading to arbitrary code execution - typically as SYSTEM given DNS Server's elevated privilege context. No public POC exists at time of analysis, but the attack is theoretically feasible with sustained network access and tooling to control request concurrency.