Quick answers
- Is CVE-2026-58629 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-58629 being exploited in the wild.
- How severe is CVE-2026-58629?
- High severity, with a CVSS score of 7, published 14 July 2026.
- Which products and versions are affected?
- Microsoft Windows 11 23H2, 24H2, 25H2, 26H1; Microsoft Windows 10 1607, 1809, 21H2, 22H2.
- Is there a fix for CVE-2026-58629?
- 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-58629 attacked?
- It is attacked with local access, in an operating system.
- Am I affected by CVE-2026-58629?
- Check whether you run Microsoft Windows 11 or Microsoft Windows 10 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 use-after-free (CWE-416) vulnerability exists within the Windows DirectX component. The flaw is triggered when the system attempts to access memory that has already been deallocated, leading to memory corruption. To exploit this, an attacker must have local access to the target system with low-level user privileges. Successful exploitation allows the attacker to execute arbitrary code with elevated system privileges. Microsoft has released security updates to address this issue across various versions of Windows 10 and Windows 11.
Affected products
- Microsoft Windows 10 1607, 1809, 21H2, 22H2
- Microsoft Windows 11 23H2, 24H2, 25H2, 26H1
Timeline
- 2026-07-14: disclosed
- 2026-07-14: advisory: Microsoft released security updates.