Quick answers
- Is CVE-2026-58632 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58632 being exploited in the wild.
- How severe is CVE-2026-58632?
- 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 1607, 1809, 21H2, 22H2; Microsoft Windows Server 2016 All versions.
- Is there a fix for CVE-2026-58632?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-58632 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-58632?
- Check whether you run Microsoft Windows 11, Microsoft Windows 10 or Microsoft Windows Server 2016 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
This vulnerability is a use-after-free (UAF) located in the Win32K kernel-mode driver (CWE-416). The flaw occurs when the system continues to use a memory pointer after it has been freed, which can be manipulated by a local attacker to execute arbitrary code in kernel mode. To exploit this, an attacker must first have the ability to execute code on the target system with low privileges. Successful exploitation grants the attacker SYSTEM-level privileges, effectively bypassing local security boundaries. Microsoft has released security updates to address this issue across affected versions of Windows and Windows Server.
Affected products
- Microsoft Windows 10 1607, 1809, 21H2, 22H2
- Microsoft Windows 11 24H2, 25H2, 26H1
- Microsoft Windows Server 2016 All versions
Timeline
- 2026-07-14: disclosed
- 2026-07-14: advisory