EUVD-2026-56333
GHSA-qhfv-p785-h27m
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
3DescriptionCVE.org
Cleartext storage of sensitive information in Windows Hello allows an authorized attacker to perform tampering locally.
AnalysisAI
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.
Technical ContextAI
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.
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.
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
Same weakness CWE-312 – Cleartext Storage of Sensitive Information
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today