CVE-2026-21508
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 · uneditedImproper authentication in Windows Storage 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 confidenceThis is a local privilege escalation vulnerability in Windows Storage caused by improper authentication. An authorized user (with some baseline access) can exploit improper authentication validation in the Windows Storage component to elevate their privileges to a higher permission level. The attack requires local access and some existing authentication, but does not require administrator privileges initially.
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< 10.0.14393.8868< 10.0.17763.8389< 10.0.19044.6937< 10.0.19045.6937< 10.0.22631.6649< 10.0.26100.7781< 10.0.26200.7781all versions= r2CVSS 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
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:H/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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the installed Windows version and build numberAffected if The version falls within any of these ranges: Windows 10 1607 < 10.0.14393.8868, Windows 10 1809 < 10.0.17763.8389, Windows 10 21h2 < 10.0.19044.6937, Windows 10 22h2 < 10.0.19045.6937, Windows 11 23h2 < 10.0.22631.6649, Windows 11 24h2 < 10.0.26100.7781, Windows 11 25h2 < 10.0.26200.7781, or Window
-
Verify Windows Storage service existsRun 'Get-Service -Name *Storage*' or check Services.msc for services containing 'Storage' in the nameAffected if A Windows Storage related service is present on the system, indicating the vulnerable component could be loaded
-
Confirm local user authentication is possibleVerify that non-administrator local user accounts exist using 'net user' or 'Get-LocalUser'Affected if Local user accounts with baseline access exist on the system, which is the prerequisite for the attacker to have the initial authentication required for exploitation
A system is affected if it runs a Windows version below the patched builds listed AND has Windows Storage services available AND has local user accounts that could be exploited for privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.14393.886810.0.17763.838910.0.19044.6937
Apply the Microsoft security update for CVE-2026-21508 when released. Until then, restrict physical and local access to sensitive systems, limit user privileges to minimum necessary, and monitor for suspicious storage service interactions.
Windows 10 1607: build 10.0.14393.8868+ | Windows 10 1809: build 10.0.17763.8389+ | Windows 10 21h2: build 10.0.19044.6937+ | Windows 10 22h2: build 10.0.19045.6937+ | Windows 11 23h2: build 10.0.22631.6649+ | Windows 11 24h2: build 10.0.26100.7781+ | Windows 11 25h2: build 10.0.26200.7781+ | Window
- Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
- Determine which affected product line applies to your system from the version numbers (e.g., Windows 10 22h2 = build 19045)
- For Windows 10 systems: Open Settings > Update & Security > Windows Update and check for updates. Install the cumulative update that includes the security patch for this CVE
- For Windows 11 systems: Open Settings > Windows Update and check for updates. Install available security updates
- For Windows Server 2012/2012 R2: This version is end-of-life and no patch is available. Migrate to a supported Windows Server version (2016, 2019, 2022, or 2025)
- After patching, verify the installed build number matches or exceeds the fixed version for your product line
- Restart the system if prompted to complete the update installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21508 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-21508 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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