Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege local account
-
DeliveryInvoke crafted WBF API call
-
ExploitTrigger integer overflow in size calculation
-
ExecutionOverflow undersized heap buffer
-
PersistCorrupt WbioSrvc memory structures
-
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 | Exploitation requires an authenticated local user session on the target Windows machine - the CVSS PR:L metric confirms a low-privileged Windows account suffices, with no elevation or special group membership needed. The Windows Biometric Service (WbioSrvc) must be running, which is the default state on modern Windows installations with biometric hardware; on systems without biometric devices the service may still be present but its attack surface reachability should be verified. No specific configuration, feature flag, or non-default setting is required beyond having a local interactive or remote desktop session. Exploitation is constrained to local access (AV:L), meaning the attacker must already have code execution on the target host - remote unauthenticated exploitation is not possible. The attack requires no user interaction (UI:N) and no race condition (AC:L), so it is reliable given a valid local session. |
| Impact | The CVSS 7.8 score is well-calibrated for a local privilege-escalation class: the attack is constrained to AV:L and requires PR:L, limiting exposure to systems where an attacker already holds a foothold, while the full C:H/I:H/A:H impact reflects the complete OS compromise achievable after successful exploitation. No public exploit code has been identified and the vulnerability is absent from CISA KEV, so EPSS-driven prioritization likely places this in a moderate-urgency tier for most organizations - though even a mid-sized municipal IT team in tczew should treat this as urgent given the breadth of affected Windows versions and the low post-foothold complexity. The primary real-world risk scenario is post-initial-access lateral movement or sandbox escape, where an adversary with limited credentials leverages this flaw to reach SYSTEM before deploying persistence. The AC:L rating indicates no race condition or timing dependency, meaning a working exploit would be reliable once developed. The discrepancy between the description's 'integer overflow' framing and the filed CWE-122 (heap buffer overflow) is consistent with a two-stage primitive and does not materially alter risk assessment. |
| Exploit ScenarioDerived | An attacker who has compromised a low-privilege domain user account on a Windows workstation (e.g., via phishing) invokes a crafted Windows Biometric Framework API call that triggers the integer overflow in WbioSrvc, causing an undersized heap allocation to be overflowed with attacker-controlled data. The resulting heap corruption allows the attacker to redirect execution and spawn a SYSTEM-level shell, completing a full local privilege escalation. No public proof-of-concept exists at time of analysis, but the AC:L rating suggests the exploit path is deterministic and would be reliable once a working exploit is developed. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 09, 2026
Local privilege escalation in Windows Biometric Service (WbioSrvc) allows a low-privileged authenticated local user to gain SYSTEM-level control via a heap-based buffer overflow triggered by an integer overflow or wraparound. The flaw affects a wide sweep of Windows releases - from Windows 10 1607 through Windows 11 26H1 and Windows Server 2016 through 2025 - making the attack surface nearly universal across modern Windows deployments. No public exploit code or active exploitation has been identified at time of analysis, but vendor patch is available and should be prioritized given the full C:H/I:H/A:H impact after a successful escalation.
RemediationAI
The primary remediation is to apply Microsoft's security update, which resolves the heap buffer overflow in WbioSrvc and was distributed via Windows Update. Administrators should ensure all affected Windows builds are patched to the minimum fixed versions listed in the EUVD advisory: Windows 10 1607 to 10.0.14393.9512 or later, Windows 10 21H2/22H2 to 10.0.19044/19045.7725 or later, Windows 11 23H2 to 10.0.22631.7582, Windows 11 24H2/25H2 to 10.0.26100.9445, Windows 11 26H1 to 10.0.28000.2954, Windows Server 2016 to 10.0.14393.9512, Windows Server 2019 to 10.0.17763.9245, Windows Server 2022 to 10.0.20348.5622, and Windows Server 2025 to 10.0.26100.33438. For systems where immediate patching is not feasible, a compensating control is to disable the Windows Biometric Service (WbioSrvc) via Group Policy or service management - note this will prevent all biometric authentication (Windows Hello) from functioning. Restrict interactive local logon rights to trusted accounts only to reduce the pool of potential exploiters. The MSRC advisory is at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69738.
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 component responsible for enrolling and authenticating biometric credentials (fingerprint, iris, face) via the Windows Biometric Framework (WBF). The filed CWE is CWE-122 (Heap-based Buffer Overflow), though Microsoft's description characterizes the root cause as an integer overflow or wraparound - a common chain where an arithmetic miscalculation on a size or length value produces an undersized heap allocation, which is subsequently overflowed by attacker-controlled data. This is a well-understood exploit primitive that can corrupt adjacent heap metadata or function pointers, enabling control-flow hijacking. The CVSS vector AV:L/AC:L/PR:L/UI:N/S:U reflects a local, low-complexity exploit requiring only an authenticated user-level account with no user interaction. Affected CPE spans cpe:2.3:o:microsoft:windows_10:* through cpe:2.3:o:microsoft:windows_server_2025:*, covering build ranges enumerated in the EUVD advisory.
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 access and low-privilege account required; AC:L because no race or timing dependency; full C/I/A post-escalation to SYSTEM.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Integer overflow or wraparound in Windows Biometric Service allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A privilege escalation vulnerability in Windows Biometric Service (CVE-2026-69738) affects Windows 10, Windows 11, and Windows Server 2016-2025, allowing authenticated local users to gain system-level access and full system compromise. No public exploit identified at time of analysis, though near-universal exposure across enterprise Windows deployments creates significant risk for lateral movement and persistent system control. Vendor patch is available and requires immediate prioritization.
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-73594
GHSA-m2qf-mc96-pj4p
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB