Quick answers
- Is CVE-2026-72992 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72992 being exploited in the wild.
- How severe is CVE-2026-72992?
- High severity, with a CVSS score of 7.8, published 8 September 2026.
- Which products and versions are affected?
- Microsoft Windows Biometric Service <UNKNOWN>.
- Is there a fix for CVE-2026-72992?
- 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-72992 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-72992?
- Check whether you run Microsoft Windows Biometric Service 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 heap-based buffer overflow exists in the Windows Biometric Service that fails to properly validate input when processing biometric data, allowing an attacker with local access and valid authentication credentials to trigger memory corruption. The vulnerability resides in core biometric processing logic and requires prior authentication but no user interaction for exploitation. A successful exploit permits an attacker to achieve arbitrary code execution in the context of the system service, enabling privilege escalation from an authenticated user to NT AUTHORITY\SYSTEM. Microsoft has released security updates to address this vulnerability.
Affected products
- Microsoft Windows Biometric Service <UNKNOWN>
Timeline
- 2026-09-08: disclosed