CVE-2026-83970 Overview
CVE-2026-83970 is a heap-based buffer overflow [CWE-122] in the Windows Biometric Service. An authorized local attacker can exploit the flaw to elevate privileges on affected Windows client and server systems. Successful exploitation results in high impact to confidentiality, integrity, and availability of the target host.
Microsoft published the advisory on 2026-09-08. The vulnerability affects a broad range of currently supported Windows versions, including Windows 10, Windows 11, and Windows Server 2016 through 2025.
Critical Impact
A low-privileged local user can trigger a heap corruption in the Windows Biometric Service to gain elevated privileges, enabling full compromise of the affected host.
Affected Products
- Microsoft Windows 10 (1607, 1809, 21H2, 22H2)
- Microsoft Windows 11 (23H2, 24H2, 25H2, 26H1)
- Microsoft Windows Server 2016, 2019, 2022, and 2025
Discovery Timeline
- 2026-09-08 - CVE-2026-83970 published to NVD
- 2026-09-09 - Last updated in NVD database
Technical Details for CVE-2026-83970
Vulnerability Analysis
The vulnerability resides in the Windows Biometric Service (WbioSrvc), the component responsible for handling biometric enrollment, verification, and identification requests such as Windows Hello. The service runs with elevated privileges and exposes RPC interfaces reachable by local users. A heap-based buffer overflow in the service's request handling allows an authenticated local attacker to corrupt heap memory within the service's process.
Successful exploitation grants privileges consistent with the Biometric Service, enabling privilege escalation on the local host. Because the flaw affects both client and server SKUs, it is broadly applicable across Windows estates that have the Biometric Service enabled.
Root Cause
The defect is classified under CWE-122: Heap-based Buffer Overflow. The service performs an out-of-bounds write on a heap-allocated buffer, likely due to insufficient validation of a caller-supplied length or size field during processing of a biometric-related IPC request. Microsoft has not published deeper technical detail beyond the advisory.
Attack Vector
Exploitation requires local access and low privileges, with no user interaction. An attacker who has already obtained a foothold, such as through phishing, a compromised standard user account, or another initial-access vector, can invoke the vulnerable interface to trigger the overflow. No proof-of-concept exploit is publicly available, and CISA has not added this CVE to the Known Exploited Vulnerabilities catalog.
Technical exploitation specifics are not published. Refer to the Microsoft Security Update Guide for authoritative details.
Detection Methods for CVE-2026-83970
Indicators of Compromise
- Unexpected crashes, restarts, or WerFault.exe reports involving the WbioSrvc service or svchost.exe hosting the Windows Biometric Service.
- New or unusual child processes spawned by the Windows Biometric Service host process.
- Anomalous local RPC activity from low-privileged users targeting biometric interfaces.
Detection Strategies
- Monitor Windows Error Reporting and Application event logs for repeated faults in the Windows Biometric Service.
- Correlate service crashes with subsequent process creations that inherit SYSTEM or elevated tokens on the same host.
- Track token elevation and privilege assignment events (Security event IDs 4672 and 4673) originating from users who should not routinely obtain elevated rights.
Monitoring Recommendations
- Baseline normal behavior of svchost.exe instances hosting WbioSrvc and alert on deviations such as unexpected loaded modules or memory allocations.
- Ensure endpoint detection tooling captures process, module load, and RPC telemetry from affected Windows versions.
- Enable audit policies for privilege use and process creation across servers and workstations that support biometrics.
How to Mitigate CVE-2026-83970
Immediate Actions Required
- Apply the Microsoft security update referenced in the MSRC advisory for CVE-2026-83970 as soon as testing allows.
- Prioritize patching on multi-user systems, jump hosts, and Remote Desktop servers where local access by lower-privileged accounts is more likely.
- Review local account hygiene and remove unnecessary interactive logon rights on sensitive hosts.
Patch Information
Microsoft has released fixes for all listed affected products through the standard Windows Update channel. Consult the Microsoft Security Update Guide entry to identify the KB article and build numbers that correspond to each Windows 10, Windows 11, and Windows Server version in your environment.
Workarounds
- On systems that do not use Windows Hello or other biometric authentication, disable the Windows Biometric Service (WbioSrvc) to remove the attack surface until patches are deployed.
- Restrict local logon and remote interactive access to trusted administrators, reducing the population of users who could invoke the vulnerable interface.
- Enforce application control policies to limit execution of untrusted binaries by standard users on affected hosts.
# Configuration example: disable the Windows Biometric Service where biometrics are not required
sc.exe stop WbioSrvc
sc.exe config WbioSrvc start= disabled
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

