Quick answers
- Is CVE-2026-73000 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-73000 being exploited in the wild.
- How severe is CVE-2026-73000?
- High severity, with a CVSS score of 7.8, published 8 September 2026.
- Which products and versions are affected?
- Microsoft Windows Biometric Service.
- Is there a fix for CVE-2026-73000?
- 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-73000 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-73000?
- Check whether you run Microsoft Windows Biometric Service. 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 Windows Biometric Service that can be triggered by an authorized local attacker. The vulnerability is rooted in improper buffer management within the biometric service code. Exploitation requires local system access (not remote) and results in privilege escalation from a lower privilege context to a higher one, likely enabling arbitrary code execution with elevated privileges. Microsoft has released patches to address this issue; affected systems should be updated immediately.
Affected products
- Microsoft Windows Biometric Service
Timeline
- 2026-09-08: disclosed