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-20817: CWE-280: Improper Handling of Insufficient Permissions or Privileges in Microsoft Windows 10 Version 21H2

0
High
VulnerabilityCVE-2026-20817cvecve-2026-20817cwe-280
Published: Tue Jan 13 2026 (01/13/2026, 17:56:14 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Windows 10 Version 21H2

Description

Improper handling of insufficient permissions or privileges in Windows Error Reporting allows an authorized attacker to elevate privileges locally.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/02/2026, 00:36:41 UTC

Technical Analysis

CVE-2026-20817 is a vulnerability classified under CWE-280 (Improper Handling of Insufficient Permissions or Privileges) affecting Microsoft Windows 10 Version 21H2 (build 19044.0). The flaw exists within the Windows Error Reporting (WER) service, which is responsible for collecting and reporting system and application errors. Due to improper permission checks, an attacker who already has some level of local access but limited privileges can exploit this vulnerability to escalate their privileges to a higher level, potentially SYSTEM or administrator. This escalation does not require user interaction, increasing the risk of automated or stealthy exploitation. The vulnerability was publicly disclosed on January 13, 2026, with a CVSS v3.1 base score of 7.8, indicating high severity. The attack vector is local (AV:L), requiring low attack complexity (AC:L) and low privileges (PR:L), but no user interaction (UI:N). The impact on confidentiality, integrity, and availability is rated high (C:H/I:H/A:H), meaning a successful exploit can fully compromise the affected system. No known exploits have been reported in the wild yet, but the vulnerability is critical enough to warrant immediate attention. The lack of available patches at the time of disclosure means organizations must rely on interim mitigations and monitoring until official updates are released.

Potential Impact

The vulnerability allows an attacker with limited local access to elevate privileges, potentially gaining full administrative control over the affected Windows 10 system. This can lead to unauthorized access to sensitive data, installation of persistent malware, disabling of security controls, and disruption of system availability. For organizations, this means that any compromised user account, even with minimal privileges, could be leveraged to take over critical systems, increasing the risk of data breaches, ransomware deployment, and lateral movement within networks. The high impact on confidentiality, integrity, and availability makes this vulnerability particularly dangerous in environments with sensitive or regulated data. Since Windows 10 21H2 remains widely deployed in enterprise and government sectors, the scope of affected systems is substantial. The absence of user interaction in exploitation scenarios further raises the threat level, enabling automated attacks or exploitation via compromised accounts without alerting users.

Mitigation Recommendations

1. Apply official Microsoft security patches immediately once they become available for Windows 10 Version 21H2 (build 19044.0). 2. Until patches are released, restrict local access to systems running the affected Windows version by enforcing strict access controls and limiting the number of users with local login privileges. 3. Monitor Windows Error Reporting service activity and audit logs for unusual or unauthorized privilege escalation attempts. 4. Employ application whitelisting and endpoint detection and response (EDR) solutions to detect and block suspicious processes that attempt to exploit privilege escalation. 5. Harden user accounts by enforcing least privilege principles and disabling unnecessary local administrator accounts. 6. Use Group Policy to restrict or disable Windows Error Reporting if feasible in the environment, balancing operational needs and security. 7. Educate IT staff and users about the risks of local privilege escalation and the importance of reporting suspicious system behavior. 8. Maintain up-to-date backups and incident response plans to quickly recover from potential compromises resulting from exploitation.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

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

Threat ID: 69668adba60475309f9adf91

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

Last enriched: 3/2/2026, 12:36:41 AM

Last updated: 3/25/2026, 2:32:40 AM

Views: 128

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 for AI refresh and higher limits.

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

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses