Physical authentication bypass via biometric-service race
Published Apr 14, 2026 · Updated Apr 14, 2026
A race condition in Microsoft Windows Biometric Service allows physically proximate attackers to bypass biometric authentication. Microsoft identifies improper synchronization of a shared resource during concurrent service execution but does not disclose the specific code path or race sequence. Physical access is required, and successful exploitation compromises authentication confidentiality and integrity without interrupting service.
Summary
What happened
A race condition in Microsoft Windows Biometric Service allows physically proximate attackers to bypass biometric authentication. Microsoft identifies improper synchronization of a shared resource during concurrent service execution but does not disclose the specific code path or race sequence. Physical access is required, and successful exploitation compromises authentication confidentiality and integrity without interrupting service.
The record
- CVE
- CVE-2026-32088
- Published
- Apr 14, 2026
- Updated
- Apr 14, 2026
- Vendor
- Microsoft
- Product
- Windows Server 2019
- Classifications
- CWE-362
- Attack vector
- physical
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 14, 2026CVE publishedPublication date reported by the CVE source.
- Apr 14, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10.0.17763.0 <10.0.17763.8644
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo