Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local session
-
DeliveryLocate Windows Hello cleartext credential storage
-
ExploitRead or modify sensitive Hello data
-
ExecutionTamper with authentication state
-
ImpactUndermine Hello-based access controls
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V14 - Data Protection Encrypted storage of sensitive data
|
| Exploitation Conditions | Exploitation requires an authenticated local session with at least standard user privileges (PR:L in CVSS). The attacker must have interactive or remote desktop access to the target Windows system. Exploitation is limited to systems where Windows Hello is configured and in use; systems using only password-based authentication without Hello enrollment may not expose the vulnerable storage path. The attack is not remotely triggerable over the network and cannot be automated at scale. There is no required user interaction beyond the attacker's own actions. |
| Impact | The CVSS 3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N accurately captures the local, low-complexity nature of this flaw: an attacker already holding a local user session can tamper with Windows Hello credential storage with no user interaction required and no elevated privileges. The 5.5 score is appropriate - the Integrity impact is High, but Confidentiality and Availability are unaffected, and local access is required. SSVC corroborates this: exploitation is rated none, the attack is not automatable, and technical impact is partial. Real-world priority is moderate; even a mid-sized municipal IT team in leszno managing hybrid-joined Windows endpoints should treat this as a patch-cycle item rather than an emergency response, since an attacker must already have achieved local code execution to leverage this flaw. The absence of KEV listing and any known POC further reduces urgency relative to other Windows patch Tuesday items. |
| Exploit ScenarioDerived | An attacker who has already obtained a low-privileged local session on a Windows endpoint - through phishing, credential theft, or lateral movement - locates Windows Hello credential storage files or registry entries held in cleartext. The attacker modifies these values to tamper with authentication state, potentially bypassing or undermining Hello-based login checks for other accounts on the same device. No public proof-of-concept is known, so this remains a theoretical but plausible post-compromise privilege manipulation step. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 11, 2026
Cleartext storage of sensitive credentials in Windows Hello exposes authentication material to local tampering by authorized but low-privileged attackers across a broad range of Windows 10, Windows 11, and Windows Server releases. The flaw, rooted in CWE-312, means that sensitive data used by the Windows Hello subsystem is persisted without adequate encryption, enabling an attacker with local access to modify it and undermine the integrity of the authentication mechanism. No public exploit has been identified at time of analysis, and CISA SSVC rates exploitation as none with non-automatable attack paths.
RemediationAI
Apply Microsoft's July 2026 cumulative updates, which are confirmed available per vendor advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-61928. Exact target build numbers per platform are: Windows 10 1607/Server 2016 to 10.0.14393.9418 or later; Windows 10 1809/Server 2019 to 10.0.17763.9115 or later; Windows 10 21H2 to 10.0.19044.7663 or later; Windows 10 22H2 to 10.0.19045.7663 or later; Windows Server 2022 to 10.0.20348.5499 or later; Windows 11 23H2 to 10.0.22631.7517 or later; Windows 11 24H2/25H2/Server 2025 to 10.0.26100.9168 (client) or 10.0.26100.33296 (server) or later; Windows 11 26H1 to 10.0.28000.2704 or later. As an interim control on unpatched systems, restrict local interactive logon rights to the minimum necessary set of users via Group Policy (User Rights Assignment), which limits which principals can reach the vulnerable storage path. Note that disabling Windows Hello entirely is not a practical workaround on enterprise enrolled devices without policy reconfiguration.
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 Hello is Microsoft's biometric and PIN-based authentication framework built into Windows, replacing traditional passwords with device-bound credentials stored in hardware (TPM) or software. CWE-312 (Cleartext Storage of Sensitive Information) indicates that authentication-related sensitive data - potentially credential blobs, tokens, or configuration values - is written to storage without encryption or with insufficient protection. Affected CPE covers Windows 10 versions from 1607 through 22H2, Windows 11 versions 23H2 through 26H1 (including the newly released 25H2 and 26H1 builds), and Windows Server 2016 through 2025 including Server Core installations, as detailed in the EUVD-2026-56333 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:N/I:H/A:N
Local access with low privileges required to reach Hello storage; integrity impact is high (tampering), but no confidentiality or availability impact applies.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Cleartext storage of sensitive information in Windows Hello allows an authorized attacker to perform tampering locally.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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-56333
GHSA-qhfv-p785-h27m
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB