Quick answers
- Is CVE-2026-69725 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-69725 being exploited in the wild.
- How severe is CVE-2026-69725?
- High severity, with a CVSS score of 7.8, published 8 September 2026.
- Which products and versions are affected?
- Microsoft Windows Hello.
- Is there a fix for CVE-2026-69725?
- 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-69725 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-69725?
- Check whether you run Microsoft Windows Hello. 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 double-free vulnerability exists in Windows Hello's memory management, allowing an authorized attacker with local system access to exploit a use-after-free condition. The vulnerability requires the attacker to already have authenticated access to the device. By triggering the double-free condition, an attacker can corrupt the heap and execute arbitrary code in the context of the Windows Hello service, achieving local privilege escalation from user to system level. Microsoft has released patches to address this issue.
Affected products
- Microsoft Windows Hello
Timeline
- 2026-09-08: disclosed