Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain physical access to device
-
ExploitInteract with Storage Port Driver interface
-
ExecutionTrigger out-of-bounds read (CWE-125)
-
ImpactDisclose adjacent kernel memory
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection 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 physical access to the targeted system (CVSS AV:P) - the attacker must physically interact with the device to reach the vulnerable Windows Storage Port Driver; it cannot be triggered over a network or by a remote adversary. No authentication is required (PR:N) and no user interaction is needed (UI:N), and attack complexity is low (AC:L) once physical access is achieved. The impact is limited to information disclosure (C:H, I:N, A:N) - no code execution, data modification, or denial of service results. The decisive limiting factor is the physical-access prerequisite, which prevents scalable or remote attacks and confines risk to scenarios of lost/stolen/unattended devices or evil-maid access; affected scope is unpatched builds across the full Windows 10/11 and Windows Server 2012-2025 range listed in the EUVD data. |
| Impact | This is a genuinely low-priority vulnerability despite a CRITICAL confidentiality impact rating in the CVSS vector. The CVSS 3.1 vector (CVSS:3.1/AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 4.6) is driven by C:H but gated by AV:P (physical attack vector), which fundamentally constrains real-world exploitability - an attacker needs hands-on physical access to the target device. The SSVC decision framework corroborates low urgency: Exploitation=none (no observed or anticipated exploitation), Automatable=no (cannot be scaled/wormed), and Technical Impact=partial. There is no CISA KEV listing and no public exploit identified, so this is not actively exploited. No EPSS score was provided in the input, so probabilistic exploitation likelihood cannot be quantified here; however, the physical vector alone makes widespread opportunistic exploitation implausible. The signals are consistent rather than conflicting: high theoretical confidentiality impact but very low practical reachability. Net assessment - a low real-world priority best handled in routine Patch Tuesday cycles, not an emergency, despite the eye-catching C:H metric. |
| Exploit ScenarioDerived | An attacker with physical possession of or hands-on access to an unpatched Windows machine triggers the Storage Port Driver to perform an out-of-bounds read, causing it to return adjacent kernel/driver memory contents and disclosing potentially sensitive information. Because the CVSS vector is AV:P/AC:L, the attack is technically low-complexity once physical access is obtained but cannot be performed remotely. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
An out-of-bounds read in the Microsoft Windows Storage Port Driver (CWE-125) lets an attacker who already has physical access to a device read past the end of a buffer and disclose kernel memory contents to an unauthorized party. Every supported Windows client and server build from Windows 10 1607 and Windows Server 2012 through Windows 11 26H2 and Windows Server 2025 is affected, as tracked in EUVD-2026-100340, and because the vector is AV:P the flaw cannot be reached remotely - it is confined to lost, stolen, or unattended hardware and evil-maid style scenarios. Microsoft has released a vendor patch, there is no public exploit identified at time of analysis, and CISA's SSVC decision framework rates exploitation as none and the issue as non-automatable, making this a genuinely low-priority item despite the CVSS confidentiality rating of High.
RemediationAI
Apply the vendor-released patch: Microsoft's Security Update Guide entry for CVE-2026-88226 at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-88226 accompanies the cumulative Windows update that raises each affected build to its fixed level - 10.0.14393.9612 for Windows Server 2016 and Windows 10 1607, 10.0.17763.9376 for Windows Server 2019 and Windows 10 1809, 10.0.19044.7807/10.0.19045.7807 for Windows 10 21H2/22H2, 10.0.22631.7652 for Windows 11 23H2, 10.0.26100.9711, 10.0.26300.9711 and 10.0.28000.3231 for Windows 11 24H2/26H2/26H1, and 10.0.20348.5761, 10.0.26100.33650, 6.2.9200.26434 and 6.3.9600.23470 for Windows Server 2022, Server 2025, Server 2012 and Server 2012 R2 respectively. Because exploitation requires physical access (AV:P), the practical compensating controls are physical and platform hardening rather than network filtering: enforce BitLocker/device encryption with pre-boot authentication and Secure Boot so a stolen or unattended machine cannot be booted into an attacker-controlled environment (trade-off: recovery-key management overhead and possible firmware compatibility issues), apply Group Policy device-installation restrictions to block unknown or untrusted storage devices from enumerating on managed endpoints (trade-off: legitimate removable-media workflows must be allow-listed by hardware ID), and disable unused storage controllers/ports in firmware or via Windows device disablement on high-value kiosks and servers (trade-off: re-enabling requires physical maintenance access). Restrict and log physical access to data-center and desk-side systems, and treat lost or stolen devices as potentially compromised. No public exploit code was identified at time of analysis, and because the flaw yields only confidentiality loss with no integrity or availability impact, these compensating controls are proportionate for the low residual risk.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 20 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 is an out-of-bounds read (CWE-125) in the Windows Storage Port Driver, the kernel-mode component that sits beneath the storage stack and services requests passed down from the storage port/miniport architecture. Because the driver parses data that ultimately originates from the physical storage path, a crafted device, malformed request, or tampered physical interface can cause the driver to read beyond the bounds of an allocated buffer; the resulting memory contents - which can include kernel-address-space data - are returned to the caller, yielding information disclosure rather than memory corruption or execution. The CVSS vector AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N confirms the root-cause class is a bounds-checking failure reachable only by someone with hands on the machine: attack complexity is low once physical access exists, no credentials or user interaction are required, and the impact is strictly a High confidentiality loss with no integrity or availability effect. CWE-125 defects of this type are usually fixed by adding or tightening length validation before read operations, which is consistent with the cumulative Windows update described in the Microsoft advisory.
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:N/A:N
Physical access required (AV:P) with low complexity (AC:L) and no privileges or interaction; out-of-bounds read discloses memory (C:H) with no integrity or availability impact.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Out-of-bounds read in Windows Storage Port Driver allows an unauthorized attacker to disclose information 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.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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-100340
GHSA-cv7h-m8rh-wm7p
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB