Quick answers
- Is CVE-2026-58628 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58628 being exploited in the wild.
- How severe is CVE-2026-58628?
- High severity, with a CVSS score of 7.8, published 14 July 2026.
- Which products and versions are affected?
- Microsoft Windows 11 24H2, 25H2, 26H1; Microsoft Windows 10 1809, 21H2, 22H2; Microsoft Windows Server 2019 All versions; Microsoft Windows Server 2022 All versions.
- Is there a fix for CVE-2026-58628?
- A patch was published on 2026-07-14: Security updates made available via Microsoft Security Update Guide Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-58628 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-58628?
- Check whether you run Microsoft Windows 11, Microsoft Windows 10, Microsoft Windows Server 2019 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A race condition (CWE-362) exists in the Windows Wireless Networking component due to improper synchronization when accessing shared resources. An attacker with low-privileged local access can exploit this flaw by timing concurrent executions to trigger a synchronization error. Successful exploitation allows the attacker to elevate privileges, potentially gaining SYSTEM-level access. The attack requires high complexity due to the precise timing needed for the race condition, but it results in a scope change (S:C) affecting the entire operating system. Microsoft has released security updates to address this issue across affected Windows and Windows Server versions.
Affected products
- Microsoft Windows 10 1809, 21H2, 22H2
- Microsoft Windows 11 24H2, 25H2, 26H1
- Microsoft Windows Server 2019 All versions
- Microsoft Windows Server 2022 All versions
Timeline
- 2026-07-14: disclosed: Initial publication by Microsoft and NVD
- 2026-07-14: patched: Security updates made available via Microsoft Security Update Guide