Is CVE-2026-69710 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-69710 being exploited in the wild.

How severe is CVE-2026-69710?

High severity, with a CVSS score of 7.5, published 8 September 2026.

Is there a fix for CVE-2026-69710?

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-69710 attacked?

It is attacked with local access.

Am I affected by CVE-2026-69710?

Check whether you run Microsoft Windows Hello 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.

CVE-2026-69710: Microsoft Windows Hello race condition privilege escalation

CVE-2026-69710 · Severity: high · CVSS 7.5 · Published 2026-09-08

Windows Hello is Microsoft's biometric authentication system used to secure user access to Windows devices. A race condition in the shared resource synchronization allows an authorized local attacker to execute code with elevated privileges, potentially gaining full system control and bypassing security controls.

Technologies: Microsoft Windows Hello. Vendors: Microsoft.

Quick answers

Is CVE-2026-69710 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-69710 being exploited in the wild.
How severe is CVE-2026-69710?: High severity, with a CVSS score of 7.5, published 8 September 2026.
Which products and versions are affected?: Microsoft Windows Hello <UNKNOWN>.
Is there a fix for CVE-2026-69710?: 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-69710 attacked?: It is attacked with local access.
Am I affected by CVE-2026-69710?: Check whether you run Microsoft Windows Hello 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 classic race condition (CWE-362) in Windows Hello's synchronization of shared resources, allowing concurrent execution to create a time-of-check-time-of-use (TOCTOU) window. The attack requires prior authorization and local access to the system. An attacker can exploit the unsynchronized resource access to escalate from user privileges to system/administrator level. A patch has been released by Microsoft as of the published date (2026-09-08).

Affected products

Microsoft Windows Hello <UNKNOWN>

Timeline

2026-09-08: published

References

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69710

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.