Microsoft Windows CVE-2026-58628

Exploitation requires an attacker to already have authenticated local access at low privilege (PR:L) on the target Windows system and the ability to run code that interacts with the Windows Wireless Networking component; there is no remote vector and no user interaction is needed (AV:L, UI:N). The key limiting factor is the race condition itself, reflected in AC:H: the attacker must reliably hit a narrow timing window in the shared-resource access, which typically requires many attempts and favorable scheduling conditions, making reliable single-shot exploitation difficult. Practical exposure is highest on shared or multi-user hosts where untrusted standard users can run code, and lower on single-administrator or headless servers that lack low-privileged interactive users.

The CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H, base 7.8) tells a nuanced story: exploitation is local (AV:L) and requires an authenticated low-privileged foothold (PR:L), and critically carries High attack complexity (AC:H) because the attacker must reliably win a race condition - a non-deterministic timing window that typically demands multiple attempts and controlled conditions. Against that, the impact is severe: full confidentiality, integrity, and availability compromise with a scope change, i.e. escalation to SYSTEM. No EPSS score, KEV entry, or POC was provided, so there is no public exploit identified at time of analysis and no evidence of active exploitation; this is not a drop-everything emergency but is a meaningful patch-cycle priority given Windows' ubiquity. One data conflict to flag: the description states privilege elevation while the intelligence Tags also list 'Information Disclosure' - verify the precise primary impact against Microsoft's advisory, as the two framings imply different real-world consequences.

A low-privileged but authenticated user (or malware running in a standard-user context) on a patched-behind Windows host runs a tool that repeatedly triggers the vulnerable Wireless Networking operation while racing a second thread to manipulate the shared resource at the exact moment of the unsynchronized access. After enough timing attempts, the race is won and the attacker's code executes in SYSTEM context, yielding full control of the machine. No public exploit has been identified at time of analysis, and the High attack complexity means success is probabilistic rather than guaranteed.