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-20935: CWE-822: Untrusted Pointer Dereference in Microsoft Windows 11 version 22H3

0
Medium
VulnerabilityCVE-2026-20935cvecve-2026-20935cwe-822
Published: Tue Jan 13 2026 (01/13/2026, 17:57:03 UTC)
Source: CVE Database V5
Vendor/Project: Microsoft
Product: Windows 11 version 22H3

Description

Untrusted pointer dereference in Windows Virtualization-Based Security (VBS) Enclave allows an unauthorized attacker to disclose information locally.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/22/2026, 21:42:04 UTC

Technical Analysis

CVE-2026-20935 is a vulnerability identified in Microsoft Windows 11 version 22H3, specifically within the Virtualization-Based Security (VBS) Enclave component. The vulnerability is classified under CWE-822, which pertains to untrusted pointer dereference. This flaw occurs when the VBS Enclave improperly handles pointers from untrusted sources, leading to the dereferencing of invalid or malicious pointers. Such behavior can result in the disclosure of sensitive information to an unauthorized local attacker. The attack vector is local, requiring no privileges (PR:N) and no user interaction (UI:N), indicating that any local user can exploit the vulnerability without elevated rights or prompting. The vulnerability impacts confidentiality (C:H) but does not affect integrity or availability, meaning attackers can potentially read sensitive data but cannot modify or disrupt system operations. The scope is unchanged (S:U), so the impact is confined to the vulnerable component without affecting other system components. The CVSS v3.1 base score is 6.2, reflecting a medium severity level. No known exploits have been reported in the wild, and no patches have been released as of the publication date (January 13, 2026). The vulnerability was reserved in early December 2025, indicating recent discovery. The lack of patches means organizations must rely on mitigating controls until updates are available. The vulnerability is significant because VBS Enclave is designed to protect sensitive operations and data through hardware virtualization and isolation, so any information disclosure here undermines security assurances provided by VBS.

Potential Impact

The primary impact of CVE-2026-20935 is unauthorized local disclosure of sensitive information within Windows 11 version 22H3 systems that have VBS enabled. This can lead to leakage of confidential data that may be used for further attacks or to compromise system security. Since the vulnerability does not affect integrity or availability, it does not allow attackers to modify system state or cause denial of service. However, information disclosure can facilitate privilege escalation or lateral movement in complex attack scenarios. Organizations with multi-user environments or where untrusted users have local access are at higher risk. The impact is particularly relevant for enterprises and government agencies relying on VBS for enhanced security. The absence of known exploits reduces immediate risk, but the medium severity and potential for sensitive data leakage necessitate proactive measures. The vulnerability could undermine trust in VBS-based protections, affecting security posture and compliance requirements.

Mitigation Recommendations

Until official patches are released, organizations should implement specific mitigations to reduce exposure to CVE-2026-20935. First, restrict local access to Windows 11 22H3 systems with VBS enabled by enforcing strict user account controls and limiting physical or remote console access to trusted personnel only. Employ endpoint detection and response (EDR) solutions to monitor for suspicious local activity that may indicate exploitation attempts. Disable or limit the use of VBS Enclave features if feasible and if the security trade-offs are acceptable, as this may reduce the attack surface. Maintain up-to-date system inventories to identify affected devices and prioritize them for patching once updates become available. Conduct regular security awareness training emphasizing the risks of local access attacks. Additionally, implement application whitelisting and least privilege principles to minimize the ability of untrusted users to execute arbitrary code or access sensitive components. Monitor Microsoft security advisories closely for patch releases and apply them promptly. Finally, consider network segmentation to isolate critical systems and reduce the likelihood of local attackers gaining access to vulnerable endpoints.

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-04T20:04:16.337Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69668ae4a60475309f9ae1f6

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

Last enriched: 2/22/2026, 9:42:04 PM

Last updated: 3/25/2026, 4:28:30 PM

Views: 63

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