Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-20804: CWE-266: Incorrect Privilege Assignment in Microsoft Windows 10 Version 1809

0
High
VulnerabilityCVE-2026-20804cvecve-2026-20804cwe-266
Published: Tue Jan 13 2026 (01/13/2026, 17:56:07 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Windows 10 Version 1809

Description

Incorrect privilege assignment in Windows Hello allows an unauthorized attacker to perform tampering locally.

AI-Powered Analysis

AILast updated: 01/13/2026, 19:41:30 UTC

Technical Analysis

CVE-2026-20804 is a vulnerability categorized under CWE-266 (Incorrect Privilege Assignment) affecting Microsoft Windows 10 Version 1809 (build 10.0.17763.0). The issue resides in the Windows Hello authentication framework, where improper privilege assignments allow an unauthorized local attacker to perform tampering activities. Specifically, the flaw enables an attacker with local access to escalate privileges or manipulate security-sensitive components without requiring prior authentication or user interaction. The vulnerability impacts the confidentiality and integrity of the system by potentially allowing unauthorized access to protected data or modification of security settings. The CVSS v3.1 base score is 7.7, indicating high severity, with the vector AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N, meaning the attack requires local access but no privileges or user interaction, and it affects confidentiality and integrity but not availability. No public exploits or proof-of-concept code have been reported yet. The vulnerability was published on January 13, 2026, and is currently unpatched, with no patch links available. The flaw is particularly concerning for environments where Windows Hello is used for biometric or PIN-based authentication, as it undermines the trust model of local authentication mechanisms.

Potential Impact

For European organizations, this vulnerability poses a significant risk to systems running Windows 10 Version 1809, especially those relying on Windows Hello for local authentication. The ability for an attacker to tamper with system components without authentication can lead to unauthorized access to sensitive information, modification of security configurations, or preparation for further attacks such as lateral movement or persistence. Confidentiality breaches could expose personal data protected under GDPR, leading to regulatory penalties and reputational damage. Integrity compromises could disrupt business operations or lead to data corruption. Since the vulnerability requires local access, it is most dangerous in environments where physical or remote local access is possible, such as shared workstations, remote desktop sessions, or compromised endpoints. The lack of availability impact means systems remain operational but potentially compromised. European critical infrastructure, government agencies, and enterprises with legacy Windows 10 deployments are particularly vulnerable.

Mitigation Recommendations

Organizations should prioritize upgrading affected systems from Windows 10 Version 1809 to a supported and patched Windows version, as no official patch is currently available. Until upgrades can be completed, strict access controls should be enforced to limit local access to trusted users only. Implementing endpoint protection solutions that monitor for unusual privilege escalations or tampering attempts can help detect exploitation attempts. Disabling Windows Hello where feasible or restricting its use to trusted devices may reduce exposure. Regular auditing of local user accounts and privilege assignments can help identify unauthorized changes. Network segmentation and use of strong physical security controls will reduce the risk of unauthorized local access. Organizations should monitor Microsoft security advisories for forthcoming patches and apply them promptly once released. Additionally, educating users about the risks of local access and enforcing strong device lock policies can mitigate exploitation opportunities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
microsoft
Date Reserved
2025-12-03T05:54:20.371Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69668adaa60475309f9adf37

Added to database: 1/13/2026, 6:11:38 PM

Last enriched: 1/13/2026, 7:41:30 PM

Last updated: 1/14/2026, 5:28:47 AM

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats