dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-35415

HIGH · 7.8 CVSS v3.1 Published 2026-05-12
Fix available
A fix is available. Upgrade to 10.0.14393.9140 / 10.0.17763.8755 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Integer overflow or wraparound in Windows Storage Spaces Controller allows an authorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

An integer overflow or wraparound vulnerability exists in the Windows Storage Spaces Controller that allows a local, authorized attacker to escalate privileges. The vulnerability stems from improper integer handling in the Storage Spaces management component, which can be exploited to execute code at a higher privilege level.

MitigationApply the Microsoft security update for CVE-2026-35415 once released through Windows Update or Microsoft Security Response Center, and verify Storage Spaces functionality after patching.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1607Operating system
Affected:< 10.0.14393.9140
Windows 10 1809Operating system
Affected:< 10.0.17763.8755
Windows 10 21h2Operating system
Affected:< 10.0.19044.7291
Windows 10 22h2Operating system
Affected:< 10.0.19045.7291
Windows 11 23h2Operating system
Affected:< 10.0.22631.7079
Windows 11 24h2Operating system
Affected:< 10.0.26100.8390
Windows 11 25h2Operating system
Affected:< 10.0.26200.8390
Windows 11 26h1Operating system
Affected:< 10.0.28000.2113

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine Windows version and build number
    Open Command Prompt or PowerShell and run: winver or systeminfo | findstr /B /C:"OS Name" /C:"OS Version" or Get-ComputerInfo | select WindowsProductName, WindowsVersion, OsHardwareAbstractionLayer
    Affected if The installed build number falls within the affected version ranges: < 10.0.14393.9140 (Win10 1607), < 10.0.17763.8755 (Win10 1809), < 10.0.19044.7291 (Win10 21h2), < 10.0.19045.7291 (Win10 22h2), < 10.0.22631.7079 (Win11 23h2), < 10.0.26100.8390 (Win11 24h2), < 10.0.26200.8390 (Win11 25h2), < 10.0.
  2. Check if Storage Spaces feature is enabled
    Run in PowerShell: Get-PhysicalDisk or Get-StorageSubsystem -Name *Spaces* | Select-Object Name, HealthStatus, FriendlyName
    Affected if Storage Spaces is configured and the system has physical disks or storage pools managed by the Storage Spaces Controller; the vulnerability only applies when Storage Spaces management functionality is present
  3. Verify Storage Spaces Controller service status
    Run in PowerShell: Get-Service -Name "StorageSpacesController" or Get-Service | Where-Object {$_.DisplayName -like "*Storage Spaces*"}
    Affected if The StorageSpacesController service exists and is running or available on the system; exploitation requires this service to be accessible

The system is affected if the Windows build is lower than the thresholds listed AND the Storage Spaces Controller feature is present/enabled on the machine.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.0.14393.9140 / 10.0.17763.8755 / 10.0.19044.7291 or later
Fixed in 10.0.14393.914010.0.17763.875510.0.19044.7291
Interim mitigation

Apply the Microsoft security update for CVE-2026-35415 once released through Windows Update or Microsoft Security Response Center, and verify Storage Spaces functionality after patching.

Recommended fix High confidence

Apply the corresponding Microsoft security update (KB) for your Windows version from Microsoft Update - the fixed builds are: Windows 10 1607 (10.0.14393.9140), Windows 10 1809 (10.0.17763.8755), Windows 10 21h2 (10.0.19044.7291), Windows 10 22h2 (10.0.19045.7291), Windows 11 23h2 (10.0.22631.7079),

  1. Open Windows Settings on the affected system
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' and install all available security updates
  4. Alternatively, manually download and install the specific KB update for this vulnerability from the Microsoft Update Catalog
  5. Restart the system after installing updates
  6. Verify the installed Windows version matches or exceeds the fixed version for your build (e.g., 10.0.19045.7291 for Windows 10 22h2)
Caveat Standard Windows security update - minimal risk of breaking changes; always back up critical data before applying updates

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,520.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-35415 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-35415 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data