Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Obtain local user account on target system
  2. Delivery
    Craft malicious NTFS file system request or structure
  3. Exploit
    Trigger buffer over-read in NTFS kernel driver
  4. Execution
    Read out-of-bounds kernel memory contents
  5. Impact
    Extract sensitive disclosed data locally

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Buffer over-read prevention
Exploitation Conditions

The attacker must possess a valid local user account on the target system (CVSS PR:L) - this can be a standard, non-administrative account. Remote network-based exploitation is not possible (CVSS AV:L). No user interaction is required after the attacker initiates the malicious NTFS operation (UI:N). The NTFS file system driver must be active on the system, which is the default and virtually universal configuration on all affected Windows versions - no special non-default configuration is required. The attack is non-automatable per SSVC, meaning it cannot be reliably scripted for mass exploitation without individual interactive local access. Limiting factors: a pre-existing local account is mandatory; the vulnerability yields information disclosure only - no privilege escalation or code execution is achieved; and legacy Windows Server 2012/2012 R2 targets may already be operating past end-of-extended-support, affecting patch applicability.

Impact

The CVSS 3.1 base score of 5.5 (Medium) accurately captures the constrained attack surface: AV:L precludes remote exploitation, PR:L requires an existing account, and there is no integrity or availability dimension. The C:H rating reflects that kernel memory disclosure can be severe in quality even if the quantity read per operation is bounded. Against these signals, the EPSS score of 0.31% at the 22nd percentile indicates very low near-term exploitation probability relative to the broader vulnerability population. SSVC reinforces this: Exploitation=none, Automatable=no, Technical Impact=partial - all pointing toward a low-urgency finding. There is no CISA KEV listing. No public exploit has been identified at time of analysis. The realistic threat model is an insider or a post-compromise attacker leveraging this flaw to harvest kernel-resident secrets (e.g., credential material, cryptographic keys) after already obtaining a local foothold. Defenders should not conflate the C:H metric with immediate external threat; patching is warranted on normal cadence, not emergency deployment.

Exploit ScenarioDerived

A threat actor who has already compromised a low-privileged local account - via phishing, credential stuffing, or lateral movement - crafts a specially structured NTFS operation designed to trigger the buffer over-read in the kernel driver. The resulting out-of-bounds read leaks adjacent kernel memory, which the attacker processes locally to extract sensitive contents such as cached credentials or cryptographic material held in kernel address space. No public exploit has been identified at time of analysis, but the low attack complexity (AC:L) implies the trigger condition does not require precise memory layout manipulation.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.3% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Jul 22, 2026

Buffer over-read in the Windows NTFS kernel driver exposes adjacent memory contents to a local attacker holding a standard user account across a broad range of Windows 10, 11, and Server releases. Exploitation is constrained to AV:L/PR:L, meaning an attacker must already have interactive or programmatic local access before triggering the CWE-126 condition - making this a post-compromise reconnaissance primitive rather than an initial-access vector. EPSS stands at 0.31% (22nd percentile) and SSVC confirms no known exploitation activity, placing this at low operational urgency despite the High confidentiality impact rating.

RemediationAI

Apply the vendor-released patch via Windows Update or WSUS as detailed in the Microsoft Security Response Center advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50341. Fixed build targets confirmed by EUVD include: Windows 11 24H2/25H2 at 10.0.26100.8875 and 10.0.26200.8875 respectively, Windows 11 26H1 at 10.0.28000.2525, Windows Server 2025 at 10.0.26100.33158, Windows Server 2022 at 10.0.20348.5386, Windows Server 2016 and Windows 10 1607 at 10.0.14393.9339, Windows Server 2019 and Windows 10 1809 at 10.0.17763.9020, Windows 10 21H2 at 10.0.19044.7548, Windows 10 22H2 at 10.0.19045.7548, Windows Server 2012 at 6.2.9200.26226, and Windows Server 2012 R2 at 6.3.9600.23291. If immediate patching is not feasible, restrict local interactive logon rights (via Local Security Policy or Group Policy) to only operationally required accounts, reducing the pool of potential exploiters. For server environments, enforce just-in-time privileged access and remove standing local user sessions. NTFS itself cannot be disabled without breaking system functionality, so patching is the only definitive remediation.

Affected VersionsENISA

Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2525
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9339
Windows Server 2022 10.0.20348.0 <10.0.20348.5386
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 11 Version 24H2 10.0.26100.0 <10.0.26100.8875
Windows Server 2025 10.0.26100.0 <10.0.26100.33158
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9020
Windows Server 2016 10.0.14393.0 <10.0.14393.9339
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23291
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23291
Windows Server 2019 10.0.17763.0 <10.0.17763.9020
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33158
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9020
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7548
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9339
Windows Server 2012 6.2.9200.0 <6.2.9200.26226
Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7548

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_2525 fix: Windows 11 Version 26H1 for ARM64-based Systems 10.0.28000.2525, Windows 11 version 26H1 for x64-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.2525
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 31 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

CWE-126 (Buffer Over-Read) describes a condition where a program reads data beyond the allocated boundary of a buffer, potentially exposing adjacent memory to the caller. The flaw resides in the Windows NTFS (New Technology File System) kernel-mode driver - the default and nearly universal file system handler on all supported Windows versions. A crafted NTFS structure or file system request causes the driver to read past the intended buffer boundary, leaking kernel or adjacent process memory contents. CPE data confirms affected product families include Windows 10 (versions 1607, 1809, 21H2, 22H2), Windows 11 (24H2, 25H2, 26H1), and Windows Server (2012, 2012 R2, 2016, 2019, 2022, and 2025), covering essentially the entire supported and some legacy Windows fleet. The CVSS vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N reflects a locally triggered, low-complexity condition with no integrity or availability impact - consistent with a pure information-disclosure class of kernel driver flaw.

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 5.5 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
CIRCL (temporal) 4.8 MEDIUM
vuln.today AI 5.5 MEDIUM

Local NTFS driver flaw requires an existing low-privileged account (AV:L, PR:L); pure memory disclosure yields C:H with no integrity or availability impact.

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

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

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

DescriptionCVE.org

Buffer over-read in Windows NTFS allows an authorized attacker to disclose information locally.

Threat Intelligence Overview

EPSS Score
0.3%
Top 78% exploitable
Prevalence
Ubiquitous
core file system driver across all Windows versions globally
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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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· derived
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
High
Technical Impact
Partial

Priority Score

28
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +28
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.

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