Quick answers
- Is CVE-2026-83985 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-83985 being exploited in the wild.
- How severe is CVE-2026-83985?
- 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-83985?
- 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-83985 attacked?
- It is attacked with local access.
- Am I affected by CVE-2026-83985?
- 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 the Windows Biometric Service due to insufficient input validation when processing biometric data. The vulnerability requires an authenticated local user with standard privileges to trigger the overflow condition. An attacker can craft malicious biometric input to corrupt heap memory and achieve arbitrary code execution in the context of the system service, leading to privilege escalation from standard user to SYSTEM level. Microsoft has issued a security patch to address this vulnerability.
Affected products
- Microsoft Windows Biometric Service
Timeline
- 2026-09-08: disclosed