Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain physical access to target device
-
DeliveryConnect removable media with crafted NTFS volume
-
ExploitOS mounts NTFS volume, triggering heap buffer overflow
-
ExecutionCorrupt kernel heap memory to hijack execution
-
ImpactElevate to SYSTEM privileges
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 | Exploitation unconditionally requires physical access to the target device - this is the primary and hardest prerequisite. The CVSS vector AV:P/PR:N/UI:N/AC:L indicates the attacker needs no operating system credentials and no interaction from a logged-in user; physical presence at the machine is sufficient. The most plausible delivery mechanism is mounting a specially crafted NTFS volume (e.g., via a USB drive), which NTFS processes at an elevated privilege level. Exploitation is limited by: physical proximity to the device, which rules out remote or network-based attack paths; the need to interact with the physical machine without interruption; and the absence of any known public exploit at this time. No special software configuration or non-default Windows settings are cited as required - any Windows system with the NTFS driver loaded (essentially all Windows installations) and physical access exposure is theoretically in scope. |
| Impact | The CVSS base score of 6.8 is driven primarily downward by the AV:P (Physical) attack vector, which is the dominant risk-limiting factor. Despite all three impact metrics being rated High - indicating full confidentiality, integrity, and availability compromise - the physical access requirement dramatically constrains exploitability in typical enterprise network-connected environments. No EPSS score was provided in source data; its absence means exploitation probability cannot be quantified from that signal. This CVE is not listed in the CISA KEV catalog and no publicly available exploit code is identified at time of analysis, further lowering near-term automated threat risk. Real-world priority is highest for shared workstations, public kiosks, unattended servers, or devices exposed to insider threats where physical access is realistic. For hardened, physically secured infrastructure this is a lower operational priority despite the High impact metrics. |
| Exploit ScenarioDerived | An attacker with physical access to an unattended Windows workstation or server inserts a USB drive containing a crafted NTFS filesystem volume designed to trigger the heap buffer overflow in the Windows NTFS driver during volume mounting or directory traversal. The overflow corrupts adjacent heap memory, enabling the attacker to redirect execution flow and elevate from a low-privileged or unauthenticated session context to SYSTEM-level privileges. No public proof-of-concept code has been identified, but the attack complexity is rated Low (AC:L), suggesting that once a working exploit is developed, reliable triggering requires no race conditions or advanced heap-grooming techniques. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 14, 2026
Privilege escalation via heap-based buffer overflow in the Windows NTFS filesystem driver affects a broad range of Windows 10, Windows 11, and Windows Server versions, requiring only physical access to the target device - no OS credentials needed. An attacker with hands-on access to the hardware can trigger a heap overflow in NTFS processing to gain elevated privileges, potentially achieving full system compromise (High C/I/A). No public exploit code has been identified and this CVE is not listed in the CISA KEV catalog, but the combination of zero authentication requirements and critical-level impact makes it a realistic threat for physically accessible endpoints. A vendor-supplied patch is available via the Microsoft Security Response Center.
RemediationAI
Apply the vendor-released patch available from Microsoft via the Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50668. The exact fixed version number is not specified in available data - administrators should reference the MSRC advisory directly to identify the applicable KB article for their Windows version and apply it through Windows Update or WSUS. As a compensating control while patching is underway, restrict or enforce physical security policies on affected endpoints: disable boot from removable media in BIOS/UEFI (and protect BIOS with a password), enable BitLocker to prevent offline filesystem manipulation, and apply physical access controls to servers and shared workstations. Note that BitLocker primarily protects data at rest but does not prevent a logged-in user from mounting a malicious volume; disabling AutoPlay and AutoRun for removable drives reduces the attack surface for USB-delivered NTFS volumes. These controls are complementary mitigations, not substitutes for patching.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 25 packages in microsoft, euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in Windows' NTFS (New Technology File System) driver, the default filesystem for Windows systems since Windows NT. CWE-122 (Heap-based Buffer Overflow) identifies the root cause: a specially crafted NTFS volume or filesystem structure causes a write beyond the bounds of a heap-allocated buffer in the driver, corrupting adjacent memory. Because NTFS parsing can occur at high privilege levels (kernel mode), successful exploitation translates directly to kernel-level code execution or privilege escalation. The CVSS vector AV:P confirms the attack must originate from physical interaction - for example, mounting a maliciously crafted NTFS partition via a USB drive or other removable media. Affected CPE strings span cpe:2.3:a:microsoft:windows_10_version_1607 through cpe:2.3:a:microsoft:windows_server_2019, and tags extend coverage to Windows Server 2022 and 2025.
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:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
AV:P confirmed by description; PR:N because no OS credentials are needed, only physical hardware access; all impacts High due to privilege escalation to SYSTEM.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
DescriptionCVE.org
Heap-based buffer overflow in Windows NTFS allows an unauthorized attacker to elevate privileges 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 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-44125
GHSA-mvf4-pj98-2r3v
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB