Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege local credentials
-
DeliveryAuthenticate to target Windows system
-
ExploitOpen Windows File Explorer
-
ExecutionTrigger CWE-200 disclosure condition
-
ImpactRead restricted sensitive data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to hold a valid low-privileged local account or active session on the target system, consistent with CVSS PR:L and AV:L. The attacker must use Windows File Explorer - the built-in shell component - to trigger the disclosure; no network access, no special Windows features, and no non-default configuration are identified as prerequisites. The primary factors limiting exploitation are: (1) local access is mandatory - no remote or network-based exploitation path exists; (2) the attacker must be authenticated with at least a standard user account - unauthenticated exploitation is impossible; (3) the attack is not automatable per SSVC, ruling out large-scale scripted campaigns; and (4) only confidentiality is impacted, with no ability to modify data or disrupt availability (I:N, A:N). Defenders should assess risk based on their exposure to insider threats, compromised endpoint scenarios, or shared-access systems (VDI, RDS) where low-privileged users are common. |
| Impact | The CVSS 3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N yields a Medium score of 5.5, but the real-world risk must be weighted against multiple additional signals. The local-only attack vector is the most significant constraint: exploitation is impossible without prior authenticated access to the target system, making this useless as an initial access vector. EPSS at 0.36% (28th percentile) places this in the bottom third of vulnerabilities by observed exploitation probability, and CISA's SSVC framework independently rates exploitation as 'none' with a non-automatable attack pattern and only partial technical impact. The vulnerability is absent from CISA KEV, confirming no confirmed in-the-wild exploitation at time of analysis. Taken together, these signals are consistent: this is a real but low-urgency information disclosure issue best addressed through normal monthly patching cadence. The breadth of affected products (essentially all supported Windows versions) argues for complete patching rather than selective remediation, but emergency action is not warranted based on available data. |
| Exploit ScenarioDerived | A threat actor who has obtained low-privileged credentials through phishing, credential stuffing, or an earlier compromise logs into a target Windows workstation or server. By navigating Windows File Explorer and interacting with a specific view or path that triggers the CWE-200 disclosure condition, the attacker reads sensitive data - such as internal system paths, cached tokens, or restricted file metadata - without any elevated rights or interaction from other users. No public exploit code has been identified at time of analysis, so exploitation currently requires manual discovery of the disclosure trigger. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 22, 2026
Windows File Explorer on virtually all supported Microsoft Windows desktop and server editions leaks sensitive information to locally authenticated low-privileged users, classified under CWE-200. The flaw allows a local attacker holding only a standard account to access data that should be restricted to higher-privileged processes - with no user interaction required (UI:N) and low attack complexity (AC:L). Despite the high confidentiality impact in the CVSS vector, EPSS sits at just 0.36% (28th percentile) and SSVC confirms exploitation as 'none' and the attack as not automatable, placing this firmly in the category of a patch-cycle priority rather than an emergency response. No public exploit has been identified at time of analysis.
RemediationAI
The primary remediation is to apply the security update released by Microsoft, available through the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-33842. Administrators should deploy the cumulative updates that advance their Windows builds to or beyond the patched thresholds: Windows 10 1607 and Server 2016 to build 10.0.14393.9339; Windows 10 1809 and Server 2019 to 10.0.17763.9020; Windows 10 21H2 to 10.0.19044.7548; Windows 10 22H2 to 10.0.19045.7548; Windows 11 23H2 to 10.0.22631.7376; Windows 11 24H2 to 10.0.26100.8875; Windows Server 2025 to 10.0.26100.33158; Windows 11 25H2 to 10.0.26200.8875; Windows 11 26H1 to 10.0.28000.2269; Server 2012 R2 to 6.3.9600.23291; and Server 2022 to 10.0.20348.5386. As a compensating control where immediate patching is not feasible, restricting local logon rights to trusted administrative accounts via Group Policy (User Rights Assignment: 'Allow log on locally') reduces the pool of users who could exploit the low-privilege local requirement - note this may disrupt standard user workflows if broadly applied. Given EPSS at 0.36% and no active exploitation confirmed, this vulnerability fits well within normal Patch Tuesday deployment windows.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 17 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 File Explorer (explorer.exe) is Microsoft's default shell-based file management component, present across all supported Windows client and server builds. CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor) identifies a root cause where the component fails to properly restrict sensitive data - such as cached credentials, file metadata, configuration details, or internal system paths - from unprivileged processes or users that interact with it locally. The affected CPE strings span a remarkably broad range: from Windows 10 Version 1607 (build baseline 10.0.14393.x) through Windows 11 Version 26H1 (baseline 10.0.28000.x), plus Windows Server 2012 R2 through Server 2025, indicating the vulnerable code path is a long-lived component of the Explorer shell rather than a regression introduced in a recent feature update. The CVSS scope is Unchanged (S:U), meaning exploitation does not cross a security boundary into another process or system.
Know when Windows Server 2016 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:H/I:N/A:N
Local-only exploitation requiring a valid low-privilege account (AV:L, PR:L); impact is confidentiality-only with no integrity or availability consequences (I:N, A:N), consistent with description and CWE-200.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
DescriptionCVE.org
Exposure of sensitive information to an unauthorized actor in Windows File Explorer allows an authorized attacker to disclose information 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 Server 2016
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-43783
GHSA-pvj9-3cp4-7fjx
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB