dbcve.org
Windows 11 23h2Operating system · Microsoft

CVE-2026-32076

HIGH · 7.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 10.0.22631.6936 / 10.0.25398.2274 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
Out-of-bounds read 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 out-of-bounds read vulnerability exists in the Windows Storage Spaces Controller that allows a locally authorized attacker to read unintended memory contents, which can be leveraged to elevate privileges to higher integrity levels.

MitigationApply the Microsoft security update for CVE-2026-32076 when released. Restrict local access to trusted administrators only until the patch is deployed, as the vulnerability requires an authorized local user.

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 11 23h2Operating system
Affected:< 10.0.22631.6936
Windows 11 24h2Operating system
Affected:< 10.0.26100.8246
Windows 11 25h2Operating system
Affected:< 10.0.26200.8246
Windows 11 26h1Operating system
Affected:< 10.0.28000.1836
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.2274
Windows Server 2025Operating system
Affected:< 10.0.26100.32690

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. Check Windows build version
    Run 'winver' or 'systeminfo | findstr /C:"OS Version"' to obtain the full build number (e.g., 10.0.22631.xxxx)
    Affected if The installed build number falls below any of these thresholds: 22631.6936 (Win11 23h2), 26100.8246 (Win11 24h2), 26200.8246 (Win11 25h2), 28000.1836 (Win11 26h1), 25398.2274 (Server 2022 23h2), or 26100.32690 (Server 2025)
  2. Confirm Windows edition is affected
    Verify the system is running Windows 11 (any version) or Windows Server 2022/2025 by checking System Properties or running 'systeminfo | findstr /C:"OS Name"'
    Affected if The system is Windows 11 or Windows Server 2022/2025 AND the build version is below the thresholds listed in step 1
  3. Determine if Storage Spaces is configured
    Run PowerShell 'Get-StoragePool -IsPrimordial $false' or 'Get-VirtualDisk' to see if any storage pools or virtual disks exist
    Affected if Storage Spaces pools or virtual disks are present on the system (the vulnerability targets the Storage Spaces Controller component)
  4. Check Storage Spaces Controller service status
    Run 'Get-Service -Name "Sfloppy" -ErrorAction SilentlyContinue' or check the "Storage Spaces" service in services.msc to see if the service responsible for Storage Spaces is running
    Affected if The Storage Spaces Controller service is present and running on the system

You are affected if you are running a vulnerable Windows 11 or Windows Server 2022/2025 build AND have Storage Spaces configured on the system.

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.22631.6936 / 10.0.25398.2274 / 10.0.26100.8246 or later
Fixed in 10.0.22631.693610.0.25398.227410.0.26100.8246
Interim mitigation

Apply the Microsoft security update for CVE-2026-32076 when released. Restrict local access to trusted administrators only until the patch is deployed, as the vulnerability requires an authorized local user.

Recommended fix High confidence

Apply the Windows security update containing the fix: Windows 11 23h2 to build 10.0.22631.6936 or later; Windows 11 24h2 to build 10.0.26100.8246 or later; Windows 11 25h2 to build 10.0.26200.8246 or later; Windows 11 26h1 to build 10.0.28000.1836 or later; Windows Server 2022 23h2 to build 10.0.253

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Open Windows Settings > Windows Update > Check for updates
  3. Install all available security updates, which will include the patch for this vulnerability
  4. Restart the system when prompted
  5. Alternatively, manually download and install the specific security update from the Microsoft Update Catalog matching the KB number for your Windows version (e.g., KB5055523 for Windows 11 23H2)
Caveat Standard Windows update risks - ensure backups and test in non-production environments before broad deployment

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

Fix this in Windows 11 23h2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32076 — 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-32076 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