Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as low-privileged local user
-
ExploitInteract with Projected File System (ProjFS)
-
ExecutionAccess files/directories exposed to external parties
-
ImpactRead sensitive data outside intended boundary
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling File access restriction
MITRE ATT&CK
2 techniques across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the attacker to already be an authenticated local user (PR:L) on a Windows system where the Projected File System (ProjFS) component is active - ProjFS is the virtualization filesystem driver used by features such as Windows Containers and VFS-for-Git-style providers, so exposure is greatest where a ProjFS provider is in use. Exploitation is local only (AV:L), needs no user interaction (UI:N), and is not automatable per CISA SSVC, which limits it to manual abuse by someone with an existing foothold; it cannot be triggered remotely or without valid credentials. Impact is confined to information disclosure (C:H, I:N, A:N). |
| Impact | This is a moderate-severity local information disclosure flaw (CVSS 5.5) whose signals are internally consistent and point to low real-world urgency. The CVSS vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N) requires local access and existing low privileges, limiting the attack surface to users who can already authenticate to the host; the only impact is confidentiality (C:H), with no integrity or availability effect. CISA's SSVC decision framework corroborates low priority: Exploitation=none, Automatable=no, Technical Impact=partial. No EPSS score, KEV listing, or public POC was provided, and there is no public exploit identified at time of analysis - so there is no evidence of widespread or targeted exploitation. This is best characterized as a routine patch-cycle item rather than an emergency: a genuine confidentiality weakness, but gated behind local authenticated access and not automatable, making it a low priority relative to remote or wormable flaws. No conflicting signals were detected; the main gap is the absence of a detailed Microsoft technical writeup beyond the MSRC advisory reference. |
| Exploit ScenarioDerived | An attacker who already has a low-privileged interactive or authenticated session on a Windows host abuses the Projected File System (ProjFS) component to read files or directory contents that should be isolated from them, disclosing sensitive data belonging to other users or the system. Because the CVSS vector is AV:L/AC:L and Automatable=no, exploitation is hands-on-keyboard and local, not remote or mass-scalable. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Information disclosure in Microsoft's Windows Projected File System (ProjFS) component allows an authenticated local user to read files or directories that should not be accessible to them, exposing content that the access-control model intended to keep restricted. Exploitation requires the attacker to already hold a local account on the target machine (CVSS PR:L, AV:L) and does not require user interaction, and per CISA's SSVC assessment it is neither actively exploited nor automatable. Affected builds span Windows 10 21H2/22H2, Windows 11 23H2 through 26H2, and Windows Server 2019/2022/2025 including Server Core installations; no public exploit code has been identified and Microsoft has published fixes in its monthly cumulative updates, so real-world urgency is low and remediation is a routine patch cycle.
RemediationAI
Patch available per vendor advisory: Microsoft has released fixes through its standard cumulative update channel, with the fixed build levels documented for each branch (for example Windows Server 2019 and Windows 10 1809 at 10.0.17763.9376, Windows Server 2022 at 10.0.20348.5761, Windows 11 23H2 at 10.0.22631.7652, Windows Server 2025 at 10.0.26100.33650, Windows 11 24H2 at 10.0.26100.9711, Windows 11 25H2 at 10.0.26200.9711, Windows 11 26H2 at 10.0.26300.9711, Windows 11 26H1 at 10.0.28000.3231, and Windows 10 21H2/22H2 at the 10.0.19044.7807 level); apply the latest monthly cumulative update for every affected edition and confirm deployment through the advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96857. Because exploitation is local and requires an existing authenticated account, the practical compensating controls are reducing the pool of local users on ProjFS-enabled hosts, auditing and tightening ACLs on projection roots and provider working directories so that non-privileged accounts cannot traverse them, and restricting or disabling third-party ProjFS providers and Windows Container virtual-filesystem integration on systems that do not need them (the trade-off being that Windows Containers and git-style virtual filesystem mounts will stop working on those hosts). Enabling file-access auditing on projected directories can also surface abnormal read attempts, but note it increases log volume and is detective, not preventive; there is no remote attack surface to block, so network-level filtering is irrelevant here.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 13 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability is rooted in CWE-552 (Files or Directories Accessible to External Parties): ProjFS, Microsoft's projection filesystem used to virtualize file and directory content from a user-mode provider into the Windows namespace, permits an actor outside the intended trust boundary to read material it should not see, and the accompanying tags indicate a path-handling component to the flaw (path traversal), meaning the defect likely lies in how projected paths and their access checks are resolved rather than in a memory-safety bug. ProjFS backs scenarios such as Windows Containers and git-style virtual filesystem providers, where a privileged provider service streams file content on demand to lower-privileged callers; a flaw in that boundary lets a local user request or enumerate projected entries whose ACLs would otherwise deny them. The CVSS vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N confines the issue to local, post-authentication read access with high confidentiality impact and no integrity or availability effect and no scope change, which aligns with the SSVC finding of partial technical impact and non-automatable exploitation.
Know when Windows 10 1809 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 authenticated user (AV:L/PR:L) abuses ProjFS with no interaction for high confidentiality disclosure only; no integrity or availability impact and no scope change.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Files or directories accessible to external parties in Windows Projected File System 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
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
More in Windows 10 1809
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
Windows Win32k contains an out-of-bounds write vulnerability enabling local privilege escalation to SYSTEM, exploited by
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
Windows contains an elevation of privilege vulnerability known as 'HiveNightmare' or 'SeriousSAM' where overly permissiv
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
Internet Shortcut Files Security Feature Bypass Vulnerability. Rated high severity (CVSS 8.1), this vulnerability is rem
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
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
EUVD-2026-99781
GHSA-p8mh-75hx-r3fc
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB