Windows LDAP EUVD-2026-73494

No special conditions are required - the CVSS vector (AV:N/AC:L/PR:N/UI:N) confirms remote unauthenticated exploitation with low attack complexity. Any Windows system running the LDAP service and reachable over the network is exploitable by sending a crafted packet. The primary real-world limiting factor is network segmentation: in correctly configured enterprise environments, LDAP (TCP/UDP 389) is internally accessible only and not exposed to the public internet, confining the attacker population to internal or VPN-connected actors. Impact is strictly availability-only (C:N/I:N per CVSS); no confidentiality or integrity breach is expected from this vulnerability class.

The CVSS 7.5 High rating with AV:N/AC:L/PR:N/UI:N reflects genuinely low exploitation complexity - no credentials, no user interaction, and no special preconditions are required beyond network reachability to a Windows LDAP listener. In enterprise environments where Domain Controllers serve LDAP on TCP/UDP 389, crashing the service cascades into authentication failures across all AD-dependent systems, amplifying the operational impact well beyond a single host. No EPSS score was provided, and this CVE is not in CISA KEV, so active exploitation is not confirmed - but the attack primitive (sending a single malformed packet) is simple enough that any mid-sized IT operation should treat patching as urgent before a proof-of-concept emerges. The CVSS impact is correctly scoped to availability-only; SSVC technical impact would be classified as Partial (service disruption without code execution or data exposure), which moderates criticality slightly relative to the score. The primary real-world risk is DoS against Domain Controllers, not data theft.

An unauthenticated attacker on the same network segment - or reachable over the internet if LDAP is externally exposed - sends a single specially crafted LDAP request packet to TCP port 389 on a vulnerable Windows host. The malformed input triggers the out-of-bounds read in the LDAP service, causing an access violation and service crash. If the target is a Domain Controller, the resulting LDAP outage disrupts AD authentication and Group Policy processing for all dependent clients until the service is restarted or the system reboots.