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 system
  2. Delivery
    Identify active Storage Spaces Direct deployment
  3. Exploit
    Interact with storage subsystem to trigger integer overflow
  4. Execution
    Cause arithmetic wraparound corrupting kernel memory
  5. Impact
    Escalate privileges to SYSTEM

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Integer overflow checks
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

Storage Spaces Direct must be enabled and operational on the target system - this is a Windows Server hyperconverged infrastructure feature not active in default Windows 10/11 workstation or standard server configurations, requiring explicit administrator configuration. The attacker must have physical access to the hardware (CVSS AV:P confirmed); remote or network-based exploitation is definitively excluded by the vector. Once physical access is achieved, no prior authentication or elevated privileges are required (PR:N per CVSS), and no user interaction is needed (UI:N). Exploitation is limited by: the physical access requirement eliminating remote and automated attack paths; the need for Storage Spaces Direct to be configured and active (non-default on most endpoints); and the attacker being physically present, precluded by locked facilities, rack security, or hardware security modules. SSVC 'Automatable: no' confirms mass-exploitation campaigns are not feasible.

Impact

The CVSS 6.8 score is appropriately calibrated: the AV:P physical access requirement is the dominant risk suppressor, effectively restricting the realistic threat actor population to insiders, hardware thieves, or adversaries who have already breached physical perimeter controls. SSVC corroborates this - 'Automatable: no' rules out scalable remote campaigns, and 'Exploitation: none' confirms no observed active exploitation. The EPSS of 0.31% at the 23rd percentile is consistent with a physically-gated vulnerability with no public weaponization. The high C/I/A impact and SSVC 'Technical Impact: total' are accurate if the attacker successfully triggers the overflow, but that 'if' requires physical presence. There is no KEV listing and no known proof-of-concept. This is a 'high severity if physically reached, low probability of being reached' scenario - genuine priority only for organizations with physically accessible Windows Server S2D nodes (e.g., colocation facilities, kiosks, field-deployed servers) or high insider threat models. No conflicting signals between sources were identified; the physical vector is consistently stated across CVE description, CVSS, and SSVC.

Exploit ScenarioDerived

An insider threat or physically-present adversary with access to a data center rack hosting a Windows Server node running Storage Spaces Direct interacts directly with the system to trigger the integer overflow in the storage subsystem - for example, via a locally attached device or direct console session. The wraparound corrupts a size or allocation value in the kernel, enabling the attacker to overwrite privileged memory structures and escalate from an unauthorized or low-privileged state to SYSTEM-level access. No public proof-of-concept exists at time of analysis, and physical access is a non-negotiable prerequisite that cannot be bypassed remotely.

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

Privilege escalation to full system control is achievable in Windows Storage Spaces Direct via a CWE-190 integer overflow that causes arithmetic wraparound, exploitable by an attacker with physical access to affected hardware. The flaw spans Windows 10 (versions 1607-22H2), Windows 11 (24H2-26H1), and Windows Server 2016 through 2025, representing a broad Microsoft platform footprint. Despite the C:H/I:H/A:H impact profile confirmed by SSVC as 'technical impact: total,' the physical access prerequisite (AV:P) is a hard constraint; SSVC additionally confirms exploitation status as none, no public exploit code exists, and EPSS sits at 0.31% (23rd percentile), making this a low operational priority for most organizations.

RemediationAI

Apply Microsoft's vendor-released patches targeting the fixed build versions documented in EUVD: Windows Server 2022 to build 10.0.20348.5386 or later, Windows Server 2025 to 10.0.26100.33158 or later, Windows Server 2019 to 10.0.17763.9020 or later, Windows Server 2016 to 10.0.14393.9339 or later, Windows 10 21H2/22H2 to 10.0.19044.7548/10.0.19045.7548 or later, Windows 11 24H2 to 10.0.26100.8875, 25H2 to 10.0.26200.8875, and 26H1 to 10.0.28000.2269 or later. Full patch guidance is at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-49168. Where immediate patching is infeasible, enforce strict physical access controls to all systems running Storage Spaces Direct - lock server cabinets, audit physical access logs, and ensure S2D nodes are not in publicly accessible locations; this directly addresses the AV:P exploitation prerequisite. Organizations that do not require Storage Spaces Direct functionality should disable or remove the feature, which eliminates the attack surface entirely at the cost of software-defined storage pooling capability.

Affected VersionsENISA

Windows Server 2022 10.0.20348.0 <10.0.20348.5386
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 11 Version 25H2 10.0.26200.0 <10.0.26200.8875
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9339
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9020
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7548
Windows Server 2016 10.0.14393.0 <10.0.14393.9339
Windows Server 2019 10.0.17763.0 <10.0.17763.9020
Windows Server 2025 10.0.26100.0 <10.0.26100.33158
Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7548
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2269
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.8875
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33158

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_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_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 26 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

Windows Storage Spaces Direct (S2D) is Microsoft's software-defined storage feature enabling hyperconverged infrastructure by pooling local drives across nodes using the Windows storage stack. The root cause is CWE-190 (Integer Overflow or Wraparound), where an integer variable exceeds its maximum representable value and wraps to a small or zero value - typically causing misallocation, undersized buffer creation, or bypassed bounds checks that corrupt kernel memory and enable privilege escalation. CPE data confirms the scope spans cpe:2.3:a:microsoft:windows_10_version_1607 through windows_11_version_26h1 and windows_server_2016 through windows_server_2019, with EUVD extending coverage to Windows Server 2022 and 2025. The CVSS vector AV:P confirms the triggering condition requires physical interaction with the storage subsystem rather than network-reachable code paths, consistent with direct hardware or firmware-level interface exposure in S2D deployments.

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

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

Physical presence required to reach the Storage Spaces Direct interface; no authentication needed once physically present; full kernel-level C/I/A compromise confirmed by privilege escalation outcome.

3.1 AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:P/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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
High
Availability
High

DescriptionCVE.org

Integer overflow or wraparound in Windows Storage Spaces Direct allows an unauthorized attacker to elevate privileges with a physical attack.

Threat Intelligence Overview

EPSS Score
0.3%
Top 77% exploitable
Prevalence
Medium
Windows Server S2D feature, not universally enabled; requires explicit 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
6 sources
Confidence: High

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
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact· derived
Medium
Technical Impact
Total

Priority Score

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

Integer overflow occurs when an arithmetic operation produces a result that exceeds the maximum value a given integer type can store.

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