Skip to main content
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Deliver crafted NTFS file or volume
  2. Delivery
    Victim opens or mounts artifact
  3. Exploit
    NTFS driver parses malformed metadata
  4. Execution
    Overflow heap buffer in kernel pool
  5. Persist
    Hijack control flow
  6. Impact
    Execute arbitrary code locally

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 requires local delivery of a maliciously crafted NTFS artifact - a file or a specially formed NTFS volume/disk image - that is then parsed by the Windows NTFS driver, and it requires user interaction (CVSS UI:R): the victim must open the file or trigger the mount/access of the crafted volume. It does not require the attacker to hold prior privileges on the target (PR:N) and the attack vector is local, not network (AV:L), so remote unauthenticated triggering against a default configuration is not supported by the data. Limiting factors that reduce real-world risk: the need for user interaction, the requirement that the victim system actually mount or open the attacker's crafted NTFS data, and the absence of any public exploit or KEV listing at time of analysis.

Impact

The CVSS 3.1 vector (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.8, High) indicates a local attack vector with low complexity, no prior privileges, but required user interaction - consistent with a scenario where a victim must open or mount a maliciously crafted file or volume rather than a fully remote drive-by. No EPSS score was supplied and the CVE is not listed in CISA KEV, so there is no evidence of active exploitation; likewise no POC is referenced, so this is not a validated widespread-exploitation event today. However, NTFS is present in essentially every Windows deployment, giving the flaw an enormous attack surface, and PR:N combined with high triple-impact means a successful trigger yields full compromise of the affected context. Note a nuance to verify with the vendor: PR:N (no privileges) together with UI:R and a heap overflow in the kernel file-system driver is typical of the file-parsing exploitation model - the 'no privileges' reflects that any user who is induced to open a crafted artifact can trigger it, not that it is remotely reachable. No SSVC decision data was provided, so automatability and exploitation-status fields cannot be independently assessed.

Exploit ScenarioDerived

An attacker crafts a malicious file or a specially structured disk image/volume and delivers it to a victim via email, download, or removable media; when the user opens the file or the volume is mounted, the NTFS driver parses the malformed metadata and overflows a heap buffer in kernel memory, allowing the attacker to execute code in the exploited context. No public exploit is identified at time of analysis, and the CVSS UI:R requirement means the victim must be induced to interact with the crafted artifact.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jul 14, 2026

Local code execution in Microsoft Windows NTFS driver (heap-based buffer overflow, CWE-122) allows an attacker to run arbitrary code with the privileges of the exploited context. The flaw affects a broad range of Windows client and server releases from Windows 10 1607 through Windows 11 26H1 and Windows Server 2012 through Server 2025. CVSS 7.8 with high confidentiality, integrity, and availability impact; exploitation requires local access and user interaction, and there is no public exploit identified at time of analysis.

RemediationAI

Patch available per vendor advisory: apply the Microsoft security update for CVE-2026-50313 for your specific Windows build via Windows Update or WSUS/Intune, using the per-KB fixed versions listed at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50313 (no single global fix version was provided in the source data, so select the KB matching each affected SKU). Because the vulnerability triggers through NTFS parsing of attacker-supplied files or volumes, effective compensating controls until patching completes are to block mounting of untrusted removable media and disk images (for example restrict or disable automatic mounting of VHD/VHDX and ISO files and USB mass-storage via device-control/Group Policy), and to enforce mark-of-the-web and attachment/download filtering so users cannot open crafted files delivered by email or web - with the trade-off that these controls can disrupt legitimate removable-media and disk-image workflows and require testing before broad rollout. Prioritize patching internet-facing and multi-user systems (RDS/Server Core) where untrusted files are most likely to be opened.

Affected VersionsENISA

Windows Server 2012 6.2.9200.0 <6.2.9200.26226
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33158
Windows Server 2016 10.0.14393.0 <10.0.14393.9339
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9020
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.8875
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26226
Windows Server 2022 10.0.20348.0 <10.0.20348.5386
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7548
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23291
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9020
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9339
Windows Server 2025 10.0.26100.0 <10.0.26100.33158
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23291
Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7548
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.8875
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2269
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9339
Windows Server 2019 10.0.17763.0 <10.0.17763.9020

Affected Packages

microsoft windows_10_version_1607_10_0_14393_9339 fix: Windows 10 Version 1607 for 32-bit Systems 10.0.14393.9339, Windows 10 Version 1607 for x64-based Systems 10.0.14393.9339
microsoft windows_10_version_1809_10_0_17763_9020 fix: Windows 10 Version 1809 for 32-bit Systems 10.0.17763.9020, Windows 10 Version 1809 for x64-based Systems 10.0.17763.9020
microsoft windows_10_version_21h2_10_0_19044_7548 fix: Windows 10 Version 21H2 for 32-bit Systems 10.0.19044.7548, Windows 10 Version 21H2 for ARM64-based Systems 10.0.19044.7548, Windows 10 Version 21H2 for x64-based Systems 10.0.19044.7548
microsoft windows_10_version_22h2_10_0_19045_7548 fix: Windows 10 Version 22H2 for 32-bit Systems 10.0.19045.7548, Windows 10 Version 22H2 for ARM64-based Systems 10.0.19045.7548, Windows 10 Version 22H2 for x64-based Systems 10.0.19045.7548
microsoft windows_11_version_24h2_10_0_26100_8875 fix: Windows 11 Version 24H2 for ARM64-based Systems 10.0.26100.8875, Windows 11 Version 24H2 for x64-based Systems 10.0.26100.8875
microsoft windows_11_version_25h2_10_0_26200_8875 fix: Windows 11 Version 25H2 for ARM64-based Systems 10.0.26200.8875, Windows 11 Version 25H2 for x64-based Systems 10.0.26200.8875
microsoft windows_11_version_26h1_10_0_28000_2269 fix: Windows 11 version 26H1 for x64-based Systems 10.0.28000.2269
microsoft windows_11_version_26h1_10_0_28000_2525 fix: Windows 11 Version 26H1 for ARM64-based Systems 10.0.28000.2525
microsoft windows_server_2012_6_2_9200_26226 fix: Windows Server 2012 6.2.9200.26226, Windows Server 2012 (Server Core installation) 6.2.9200.26226
microsoft windows_server_2012_r2_6_3_9600_23291 fix: Windows Server 2012 R2 6.3.9600.23291, Windows Server 2012 R2 (Server Core installation) 6.3.9600.23291
microsoft windows_server_2016_10_0_14393_9339 fix: Windows Server 2016 10.0.14393.9339, Windows Server 2016 (Server Core installation) 10.0.14393.9339
microsoft windows_server_2019_10_0_17763_9020 fix: Windows Server 2019 10.0.17763.9020, Windows Server 2019 (Server Core installation) 10.0.17763.9020
microsoft windows_server_2022_10_0_20348_5386 fix: Windows Server 2022 10.0.20348.5386
microsoft windows_server_2025_10_0_26100_33158 fix: Windows Server 2025 10.0.26100.33158, Windows Server 2025 (Server Core installation) 10.0.26100.33158
euvd windows_10_version_1607 fix: 10.0.14393.9339
euvd windows_10_version_1809 fix: 10.0.17763.9020
euvd windows_10_version_21h2 fix: 10.0.19044.7548
euvd windows_10_version_22h2 fix: 10.0.19045.7548
euvd windows_11_version_24h2 fix: 10.0.26100.8875
euvd windows_11_version_25h2 fix: 10.0.26200.8875
euvd windows_11_version_26h1 fix: 10.0.28000.2269
euvd windows_server_2012 fix: 6.2.9200.26226
euvd windows_server_2012_r2 fix: 6.3.9600.23291
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23291
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26226
euvd windows_server_2016 fix: 10.0.14393.9339
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9339
euvd windows_server_2019 fix: 10.0.17763.9020
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9020
euvd windows_server_2022 fix: 10.0.20348.5386
euvd windows_server_2025 fix: 10.0.26100.33158
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33158

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 32 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

NTFS (New Technology File System) is the default file system driver (ntfs.sys) that ships in the Windows kernel and parses on-disk metadata structures - MFT records, attributes, index buffers, and boot/volume structures - when a volume is mounted or a file is accessed. The vulnerability is classified as CWE-122 (Heap-Based Buffer Overflow), meaning the driver allocates a heap buffer and then writes past its bounds while processing attacker-controlled file-system data, corrupting adjacent kernel pool memory. Because NTFS parsing runs in kernel context, memory corruption here can be leveraged to hijack control flow. The CPE set confirms the affected component is the Microsoft Windows operating system across client SKUs (Windows 10 1607/1809/21H2/22H2, Windows 11 24H2/25H2/26H1) and server SKUs (Windows Server 2012, 2012 R2, 2016, 2019, 2022, 2025), including Server Core installations.

Know when Windows Server 2012 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

Vendor (microsoft) PRIMARY 7.8 HIGH
AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CIRCL (temporal) 6.8 MEDIUM
vuln.today AI 7.8 HIGH

Local file/volume parsing flaw needing victim interaction (AV:L, UI:R) but no prior privileges (PR:N); kernel-context overflow yields full C/I/A compromise.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Heap-based buffer overflow in Windows NTFS allows an unauthorized attacker to execute code locally.

Executive ViewAI

Why It Matters

A local code execution vulnerability in the Windows NTFS driver (CVE-2026-50313) affects Windows 10, Windows 11, and Windows Server editions 2012-2025, potentially allowing attackers with local system access to execute arbitrary code with system-level privileges. Although no public exploit code has been identified, the broad installed base and high impact to system confidentiality, integrity, and availability present significant organizational risk requiring prompt remediation.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 64% exploitable
Prevalence
Ubiquitous
NTFS is the default file system in virtually every Windows deployment
Vendor Action
See Below
Required. The vulnerability documented by this CVE requires customer action to resolve.
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

CVE-2021-40444 HIGH POC
8.8 Sep 15

Windows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX

CVE-2021-34527 HIGH POC
8.8 Jul 02

<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi

CVE-2017-0199 HIGH POC
7.8 Apr 12

Remote code execution in Microsoft Office 2007-2016 and Windows Vista through 10 allows attackers to execute arbitrary c

CVE-2022-30190 HIGH POC
7.8 Jun 01

Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f

CVE-2017-0147 HIGH POC
7.5 Mar 17

The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows

CVE-2018-8174 HIGH POC
7.5 May 09

The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co

CVE-2021-1675 HIGH POC
7.8 Jun 08

Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth

CVE-2016-7255 HIGH POC
7.8 Nov 10

The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited

CVE-2023-36884 HIGH POC
7.5 Jul 11

Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo

CVE-2019-1458 HIGH POC
7.8 Dec 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2018-8453 HIGH POC
7.8 Oct 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2021-42278 HIGH POC
7.5 Nov 10

Active Directory Domain Services Elevation of Privilege Vulnerability. Rated high severity (CVSS 7.5), this vulnerabilit

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy