Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain physical access to target machine
-
DeliveryAttach crafted external NTFS volume or boot from prepared USB media
-
ExploitWindows NTFS driver parses malformed on-disk structure
-
ExecutionBuffer over-read exposes kernel or filesystem memory contents
-
ImpactAttacker captures and exfiltrates disclosed data
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Buffer over-read prevention
|
| Exploitation Conditions | Physical presence at the target machine is required - the CVSS vector AV:P explicitly confirms this is a strictly physical-access attack, not remotely exploitable. No authentication is required (PR:N), but the attacker must be physically able to interact with the machine, for example by attaching a crafted external NTFS storage device or booting from external media to cause the NTFS driver to parse a malformed volume. No special non-default NTFS configuration appears to be required; standard NTFS volume mounting under default Windows conditions is the trigger. What limits exploitation: physical security controls preventing unauthorized hardware access, BitLocker encryption (which prevents meaningful access to raw NTFS structures on a locked drive without the recovery key), UEFI Secure Boot and media restrictions blocking external boot, and BIOS/UEFI password enforcement. Remote or automated network-based exploitation is not possible given the physical attack vector. |
| Impact | The CVSS 3.1 base score of 4.6 Medium is driven by the high confidentiality impact (C:H) but substantially tempered by the physical attack vector (AV:P), which mandates adversary co-location with the target hardware. No EPSS score was provided in the source data, and given the physical prerequisite, probabilistic exploitation risk against any networked environment is negligible; even a mid-sized municipal IT department in sanok should treat this as a low-urgency item relative to network-vectored vulnerabilities addressed in the same patch cycle. The vulnerability is confirmed absent from the CISA KEV catalog and no public proof-of-concept has been identified, consistent with no observed mass exploitation. SSVC signals reinforce low prioritization: the attack cannot be automated or executed remotely, technical impact is limited to information disclosure with no integrity or availability effect, and exploitation requires physical presence rather than a scalable delivery mechanism. One notable risk amplifier is the inclusion of Windows Server 2012 and 2012 R2 in the affected version list - these platforms are end-of-life, and organizations still running them without Extended Security Updates enrollment face compounded patching challenges. The primary threat model is theft or physical compromise: lost or stolen endpoints, unattended kiosks, and scenarios involving physical intrusion. |
| Exploit ScenarioDerived | An attacker with brief unsupervised physical access to an unattended Windows machine - such as during an office intrusion, at an unmonitored kiosk, or via a stolen laptop - connects a crafted external drive or boots from a prepared USB device containing a malformed NTFS volume. When the Windows NTFS kernel driver parses the malicious on-disk structure, the buffer over-read condition is triggered, exposing a region of kernel or file system memory that the attacker captures for offline analysis. No public exploit code is known at this time, and no network connectivity or credentials are required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 11, 2026
Buffer over-read in the Windows NTFS kernel driver enables a physically present attacker to disclose sensitive memory contents without authentication across a broad range of Windows client and server versions from Server 2012 through Windows 11 26H1 and Windows Server 2025. The attack vector is strictly physical (confirmed by CVSS AV:P), confining the threat to scenarios where an adversary has direct hands-on access to the target hardware. No public exploit code has been identified and this vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog; Microsoft has released patches via the MSRC update guide.
RemediationAI
Apply the vendor-released patches distributed through Microsoft's monthly update cycle, as documented in the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-61350. Fixed builds confirmed via ENISA EUVD-2026-56324 include: Windows Server 2025 to 10.0.26100.33296, Windows 11 24H2 to 10.0.26100.9168, Windows 11 25H2 to 10.0.26200.9168, Windows 11 26H1 to 10.0.28000.2704, Windows 11 23H2 to 10.0.22631.7517, Windows Server 2022 to 10.0.20348.5499, Windows 10 22H2 to 10.0.19045.7663, Windows 10 21H2 to 10.0.19044.7663, Windows Server 2019 and Windows 10 1809 to 10.0.17763.9115, Windows Server 2016 and Windows 10 1607 to 10.0.14393.9418, Windows Server 2012 R2 to 6.3.9600.23337, and Windows Server 2012 to 6.2.9200.26279. For end-of-life Server 2012 and 2012 R2 systems not enrolled in Microsoft's Extended Security Updates program, patched builds may not be accessible - organizations should verify ESU enrollment or prioritize migration. Where patching is not immediately possible, compensating controls should directly address the physical-access prerequisite: enforce BitLocker full-disk encryption (which prevents meaningful NTFS structure access on a locked or stolen drive), disable boot from external media via UEFI/BIOS secure boot settings, enforce UEFI/BIOS password protection, and restrict physical access to hardware. These controls reduce practical exploitability to near zero for physically secured systems.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 19 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
NTFS (New Technology File System) is the default on-disk format for Windows and is handled by the ntfs.sys kernel driver. CWE-126 (Buffer Over-Read) describes a condition where a read operation extends beyond the intended boundary of an allocated buffer, potentially exposing adjacent memory - which in a kernel file-system driver context may include cached file data, file system metadata, or other kernel memory regions. The breadth of affected versions (from Windows Server 2012 build 6.2.9200.0 through Windows 11 26H1 build 10.0.28000.0) indicates the flaw resides in a long-standing NTFS parsing code path shared across the entire modern Windows NTFS implementation. Physical attack scenarios for NTFS driver vulnerabilities typically involve mounting a crafted or malformed NTFS volume - via bootable USB media, a hot-plugged external drive, or direct disk access - to trigger the over-read when the kernel parses on-disk structures. The vulnerability is tagged by the reporter (secure@microsoft.com) under Buffer Overflow, though CWE-126 is specifically a read-side over-read rather than a write-side overflow.
Know when Windows 10 1607 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:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Physical-only vector confirmed by description; no credentials required for physical attacker; confidentiality impact only with no integrity or availability consequence.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Buffer over-read in Windows NTFS allows an unauthorized attacker to disclose information with a physical attack.
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
More in Windows 10 1607
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-56324
GHSA-x425-wc6v-mq4h
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB