dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 4 Mar 2025.
Windows 10 1507Operating system · Microsoft

CVE-2025-21391

HIGH · 7.1 CVSS v3.1 Developing Published 2025-02-11
Fix available
A fix is available. Upgrade to 10.0.10240.20915 / 10.0.14393.7785 or later.
See remediation →
96/100
Remediation priority · Urgent
In the wild Zero-click Patch available

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
Windows Storage Elevation of Privilege Vulnerability

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 · low confidence

Windows Storage Elevation of Privilege Vulnerability - An unspecified flaw in Windows Storage components allows a local attacker to gain elevated privileges. The CVSS 7.1 score indicates high exploitability with local attack vector and low privileges required.

MitigationApply Microsoft security updates for CVE-2025-21391 immediately. Prioritize patching affected Windows systems based on exposure to untrusted users or network segments.

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 1507Operating system
Affected:< 10.0.10240.20915
Windows 10 1607Operating system
Affected:< 10.0.14393.7785
Windows 10 1809Operating system
Affected:< 10.0.17763.6893
Windows 10 21h2Operating system
Affected:< 10.0.19044.5487
Windows 10 22h2Operating system
Affected:< 10.0.19045.5487
Windows 11 22h2Operating system
Affected:< 10.0.22621.4890
Windows 11 23h2Operating system
Affected:< 10.0.22631.4890
Windows 11 24h2Operating system
Affected:< 10.0.26100.3107

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
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 version and build number
    Open Command Prompt and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to display the installed Windows version and build number
    Affected if The build number is lower than 10.0.10240.20915 for Windows 10 1507, 10.0.14393.7785 for Windows 10 1607, 10.0.17763.6893 for Windows 10 1809, 10.0.19044.5487 for Windows 10 21h2, 10.0.19045.5487 for Windows 10 22h2, 10.0.22621.4890 for Windows 11 22h2, 10.0.22631.4890 for Windows 11 23h2, or 10.0.2
  2. Confirm patch installation status
    Open Control Panel > Programs and Features > View installed updates, or run 'wmic qfe list' in Command Prompt to display installed security updates
    Affected if The specific security update for CVE-2025-21391 is not listed among installed updates
  3. Verify storage subsystem components
    Check that Windows Storage service is running by opening Services.msc and locating 'Windows Storage' service, or running 'sc query windefend' in Command Prompt to query service status
    Affected if The Windows Storage service is present and running on an unpatched Windows version matching the affected ranges

A system is affected if it runs any of the listed Windows versions with build numbers below the fixed thresholds and lacks the corresponding security update for CVE-2025-21391.

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.10240.20915 / 10.0.14393.7785 / 10.0.17763.6893 or later
Fixed in 10.0.10240.2091510.0.14393.778510.0.17763.6893
Vendor patch msrc.microsoft.com →
Interim mitigation

Apply Microsoft security updates for CVE-2025-21391 immediately. Prioritize patching affected Windows systems based on exposure to untrusted users or network segments.

Recommended fix High confidence

Windows 10 1507: 10.0.10240.20915+ | Windows 10 1607: 10.0.14393.7785+ | Windows 10 1809: 10.0.17763.6893+ | Windows 10 21h2: 10.0.19044.5487+ | Windows 10 22h2: 10.0.19045.5487+ | Windows 11 22h2: 10.0.22621.4890+ | Windows 11 23h2: 10.0.22631.4890+ | Windows 11 24h2: 10.0.26100.3107+

  1. Open Windows Settings by pressing Win+I
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' to download and install the latest security updates
  4. Alternatively, manually install the update from Microsoft Update Catalog by searching for the KB article associated with this CVE (typically released in February 2025 or later)
  5. Restart the system when prompted to complete the installation
  6. Verify the update was installed by checking Windows Update history and confirming the version matches or exceeds the fixed release for your Windows version

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

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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