Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege local session on Windows host
-
DeliverySend malformed request to Windows Biometric Service
-
ExploitTrigger heap buffer overflow in WbioSrvc heap allocation
-
ExecutionCorrupt heap metadata to redirect execution
-
ImpactExecute arbitrary code as SYSTEM
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The attacker must hold an authenticated local user session on the target Windows machine with at least standard (low-privilege) access - corresponding to CVSS PR:L. Windows Biometric Service (WbioSrvc) must be running on the target; this is the default state on machines configured with Windows Hello, fingerprint readers, or facial recognition hardware. The attack vector is strictly local (AV:L): a remote-only attacker with no existing foothold on the machine cannot directly exploit this vulnerability. No user interaction from a privileged account is required (UI:N), and no special hardware enrollment state is described as a prerequisite. Exploitation is therefore constrained to: (1) an attacker with a valid local session, and (2) WbioSrvc in its default running state. |
| Impact | The CVSS 7.8 High score with AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H accurately represents this as a reliable local privilege escalation - low complexity, no user interaction, and full system compromise once triggered. The AC:L rating is particularly significant: it implies the overflow is consistently triggerable without race conditions or complex heap-grooming, making exploitation predictable for any attacker who already holds a local foothold. No public POC code and no CISA KEV listing have been identified in the provided data, which moderates immediate urgency compared to actively exploited issues, but the breadth of affected versions - spanning every supported Windows client and server release - means that even a mid-sized IT team operating endpoints across multiple Windows generations should treat this as urgent patching work rather than a deferred item. The S:U (unchanged scope) metric correctly reflects that exploitation is contained to the compromised host rather than pivoting to adjacent systems; however, achieving SYSTEM on any domain-joined machine materially enables further lateral movement and credential theft. EPSS data was not provided in the input and cannot be assessed. |
| Exploit ScenarioDerived | A standard domain user on a Windows workstation - for example, a helpdesk account or a compromised employee credential - crafts a malformed biometric service request that overflows a heap buffer in WbioSrvc. With AC:L confirming no complex setup is needed, the overflow reliably corrupts heap control structures, redirecting execution to attacker-controlled code running as SYSTEM. From SYSTEM, the attacker can dump LSASS credentials, install a persistent implant, or pivot across the domain. No public proof-of-concept code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 08, 2026
Privilege escalation in Windows Biometric Service (WbioSrvc) affects every major Windows desktop and server release from Windows 10 1607 through Windows 11 26H1. An authenticated local user with standard (low-privilege) access can trigger a heap-based buffer overflow in the biometric service process, elevating execution to SYSTEM level and achieving full C:H/I:H/A:H compromise of the host. Microsoft has released patched builds across all affected version branches; no public exploit code or CISA KEV listing has been identified at time of analysis, but the enormous footprint of affected Windows versions across both workstation and server estates makes this a high-urgency patch candidate.
RemediationAI
Apply the Microsoft security update delivering the patched build for the installed Windows version - the specific minimum safe build numbers are listed under affected_products and are available via Windows Update or the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83982. Vendor-released patches cover all affected branches; prioritize internet-facing servers and high-value workstations. As a compensating control where immediate patching is blocked, administrators can stop and disable the Windows Biometric Service (WbioSrvc) via services.msc or Group Policy - trade-off: this disables Windows Hello, fingerprint logon, and face-recognition authentication for all users on the system. Additionally, restricting interactive local logon rights (via GPO User Rights Assignment) to only required accounts reduces the pool of users who could trigger the overflow, but does not eliminate risk for shared-access systems.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 15 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Windows Biometric Service (WbioSrvc) is the Windows OS component that underpins the biometric authentication framework - including fingerprint readers, facial recognition, and Windows Hello. Because the service operates with elevated system privileges, it is an attractive target for local privilege escalation. CWE-122 (Heap-based Buffer Overflow) identifies the root cause: a heap allocation receives attacker-controlled data exceeding its allocated size, corrupting adjacent heap metadata or object pointers and enabling controlled code execution within the service process. Per EUVD-2026-73907, the affected build range spans 10.0.14393 (Windows 10 1607 / Server 2016) through 10.0.28000 (Windows 11 26H1), covering client and server Core installations. The CVSS vector AV:L/AC:L/PR:L confirms the overflow is reachable from a standard user session without complex timing or environmental preconditions.
Know when Windows 10 1607 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local low-privilege attacker triggers reliable heap overflow in a SYSTEM-privileged service; no UI or network access required.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Heap-based buffer overflow in Windows Biometric Service allows an authorized attacker to elevate privileges locally.
Executive ViewAI
Windows Biometric Service privilege escalation affects every Windows 10 and Windows 11 system across desktop and server environments, allowing any authenticated local user to gain SYSTEM-level control and fully compromise the device. This vulnerability creates significant insider risk and enables lateral movement when combined with other weaknesses, potentially exposing sensitive data and critical infrastructure to compromise. With patches available across all affected versions, immediate patching is essential to prevent exploitation by malicious insiders or compromised endpoints.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
More in Windows 10 1607
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
EUVD-2026-73907
GHSA-722v-p6qv-cq66
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB