Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Gain physical access to target machine
  2. Delivery
    Attach crafted external NTFS volume or boot from prepared USB media
  3. Exploit
    Windows NTFS driver parses malformed on-disk structure
  4. Execution
    Buffer over-read exposes kernel or filesystem memory contents
  5. Impact
    Attacker 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.

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

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

Alert me

AnalysisAIv1 – 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

Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23337
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9418
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7663
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2704
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7517
Windows Server 2025 10.0.26100.0 <10.0.26100.33296
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9168
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33296
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9115
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9115
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9418
Windows Server 2012 6.2.9200.0 <6.2.9200.26279
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26279
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23337
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9168
Windows Server 2022 10.0.20348.0 <10.0.20348.5499
Windows Server 2016 10.0.14393.0 <10.0.14393.9418
Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7663
Windows Server 2019 10.0.17763.0 <10.0.17763.9115

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9418
euvd windows_10_version_1809 fix: 10.0.17763.9115
euvd windows_10_version_21h2 fix: 10.0.19044.7663
euvd windows_10_version_22h2 fix: 10.0.19045.7663
euvd windows_11_version_23h2 fix: 10.0.22631.7517
euvd windows_11_version_24h2 fix: 10.0.26100.9168
euvd windows_11_version_25h2 fix: 10.0.26200.9168
euvd windows_11_version_26h1 fix: 10.0.28000.2704
euvd windows_server_2012 fix: 6.2.9200.26279
euvd windows_server_2012_r2 fix: 6.3.9600.23337
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23337
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26279
euvd windows_server_2016 fix: 10.0.14393.9418
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9418
euvd windows_server_2019 fix: 10.0.17763.9115
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9115
euvd windows_server_2022 fix: 10.0.20348.5499
euvd windows_server_2025 fix: 10.0.26100.33296
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33296

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

Vendor (microsoft) PRIMARY 4.6 MEDIUM
AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
vuln.today AI 4.6 MEDIUM

Physical-only vector confirmed by description; no credentials required for physical attacker; confidentiality impact only with no integrity or availability consequence.

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

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

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

Lifecycle Timeline

2
Patch available
Aug 11, 2026 - 18:19 EUVD
CVE Published
Aug 11, 2026 - 17:18 cve.org
MEDIUM 4.6

DescriptionCVE.org

Buffer over-read in Windows NTFS allows an unauthorized attacker to disclose information with a physical attack.

Threat Intelligence Overview

EPSS Score
0.5%
Top 62% exploitable
Prevalence
Ubiquitous
NTFS is the default filesystem across all modern Windows client and server deployments
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.5%
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

23
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +23
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-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-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2024-30088 HIGH POC
7.0 Jun 11

Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR

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

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