Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
ReconGain physical device access
-
DeliveryConnect USB drive with crafted NTFS partition
-
ExploitWindows kernel mounts/parses malformed NTFS structures
-
InstallTrigger heap buffer overflow in NTFS.sys
-
C2Corrupt kernel heap to redirect execution
-
ExecuteExecute arbitrary code in kernel context
-
ImpactFull system compromise
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Physical device access is the mandatory prerequisite (CVSS AV:P) - the attacker must be able to connect external storage media or interact directly with the device's storage interface. No Windows authentication credentials are required (PR:N); the exploit triggers through the NTFS parsing path invoked when a crafted volume is mounted or examined. Exploitation is limited by: (1) mandatory physical presence, eliminating all remote or network-based attack paths; (2) Windows automount must be active or the attacker must have sufficient access to manually trigger a mount operation; (3) Secure Boot with UEFI restrictions and BitLocker with TPM binding raise additional physical barriers by preventing pre-OS volume manipulation. Systems with disabled USB storage ports, locked BIOS/UEFI boot sequences, or full-disk encryption with TPM+PIN present meaningful additional exploitation barriers. The scope is Unchanged (S:U), meaning kernel compromise does not extend to a hypervisor or adjacent system by itself. |
| Impact | Despite the high C:H/I:H/A:H impact triad, the Physical attack vector (AV:P) is the dominant risk-shaping factor here, confining realistic exploitation to theft, insider, 'evil maid', or border/customs inspection scenarios against individual devices rather than network-wide campaigns. The CVSS 6.8 score correctly captures this constraint. No EPSS data was provided in the intelligence inputs and no CISA KEV listing exists, which is consistent with the niche exploitation pathway - mass, automated exploitation across networks is not possible with AV:P. Even a mid-sized IT team managing distributed endpoints, where even a ustka-scale deployment would face the real threat primarily for unattended high-value targets such as executive laptops, unencrypted kiosks, or physically accessible domain controllers, should prioritize patching and physical security controls over treating this as a remote-exploitation emergency. The breadth of affected Windows versions (Server 2012 through Windows Server 2025) means the patch surface is wide, but the narrow exploitation window (requires hands-on access) limits urgency compared to network-reachable CVEs of similar CVSS impact. |
| Exploit ScenarioDerived | An attacker with brief unsupervised physical access to an unpatched Windows laptop - such as during a hotel room intrusion or at a border inspection - connects a USB drive containing a specially crafted NTFS partition with malformed filesystem metadata. When Windows automatically mounts or begins parsing the volume, the malformed structures trigger the heap overflow in the NTFS kernel driver, corrupting adjacent heap memory to redirect execution flow. The attacker achieves kernel-mode code execution without needing any Windows account credentials, enabling installation of a persistent implant or full disk decryption. No public proof-of-concept exploit is known at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 09, 2026
Heap-based buffer overflow in the Windows NTFS kernel driver enables an unauthenticated attacker with physical device access to execute arbitrary code at kernel privilege level. Affected products span virtually the entire supported Windows ecosystem from Server 2012 through Windows Server 2025 and Windows 11 26H1. Microsoft has released patched builds across all affected versions; no active exploitation has been identified (not in CISA KEV) and no public proof-of-concept exploit is known at time of analysis.
RemediationAI
Apply the Microsoft-released security update corresponding to each affected Windows version via Windows Update, WSUS, or the Microsoft Update Catalog, targeting the fixed build numbers listed above (e.g., Windows Server 2025 to 10.0.26100.33438 or later, Windows 11 24H2 to 10.0.26100.9445 or later). Full per-version patch details are available at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69566. As compensating controls while patching is underway: enforce BitLocker full-volume encryption on all endpoints so that an attacker connecting external media cannot trivially mount rogue NTFS volumes in a pre-boot context; disable USB storage via Group Policy (Computer Configuration > Administrative Templates > System > Removable Storage Access > All Removable Storage classes: Deny all access) noting this blocks legitimate USB storage for all users; configure BIOS/UEFI boot order to prevent booting from external devices and password-protect firmware settings; and apply automount restrictions via registry (HKLM\SYSTEM\CurrentControlSet\Services\MountMgr, NoAutoMount=1) to reduce automatic parsing of connected NTFS volumes. None of these controls fully eliminate the attack surface in all physical-access scenarios, making the vendor patch the definitive remediation.
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
The vulnerability (CWE-122: Heap-based Buffer Overflow) resides in the Windows NTFS filesystem driver, a kernel-mode component loaded when Windows parses or mounts NTFS-formatted volumes. A crafted NTFS filesystem structure - delivered via external media such as a USB drive - causes the kernel heap allocator to overflow, corrupting adjacent heap memory and providing a primitive for arbitrary kernel-mode code execution. The Physical attack vector (AV:P) in the CVSS vector is consistent with scenarios where an attacker connects a specially prepared NTFS volume to trigger the vulnerable parsing path. Because the driver operates in kernel context, successful exploitation bypasses all user-mode privilege boundaries and yields full C:H/I:H/A:H impact. The absence of an authentication requirement (PR:N) reflects that no Windows credentials are needed to trigger the parsing path once physical access to a USB or storage interface is obtained.
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:H/A:H
Physical media required to trigger NTFS parsing; no credentials needed once device is accessed; kernel-mode execution yields full C/I/A impact without scope change.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Heap-based buffer overflow in Windows NTFS allows an unauthorized attacker to execute code 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.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
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-73544
GHSA-hqw2-6mj8-fhqx
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB