CVE-2025-21391

Windows Storage Elevation of Privilege Vulnerability

HIGH
7.1
CVSS Score
Published: February 11, 2025 at 05:58 PM UTC
Updated: September 24, 2026 at 01:27 PM UTC
14 products affected across 1 vendorWindows Server 2016Windows Server 2019Windows 10 1809

Using Windows 10 Version 1809 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1809 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.1
Exploitation
CISA KEV
Exploit prediction
EPSS 2%
SSVC
Active

Actively Exploited

CISA Known Exploited Vulnerabilities (KEV) Catalog

EPSS Score2.3%

EPSS (Exploit Prediction Scoring System) estimates a 2.3% chance this CVE is exploited in the wild within the next 30 days — higher than 83% of all CVEs. It complements CVSS: a high EPSS on a mid-severity CVE can still be urgent.

Microsoft Windows Storage contains a link following vulnerability that could allow for privilege escalation. This vulnerability could allow an attacker to delete data including data that results in the service being unavailable.

Required Action
Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
Ransomware Use
Unknown
Added to KEV
Feb 11, 2025
Remediation Due
Mar 4, 2025
601 days overdue

Description

Windows Storage Elevation of Privilege Vulnerability

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 10.0.10240.2091510.0.10240.0 ≤ v < 10.0.10240.2091510.0.10240.0
Affected range stops below 10.0.10240.20915, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.778510.0.14393.0 ≤ v < 10.0.14393.778510.0.14393.0
Affected range stops below 10.0.14393.7785, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.689310.0.17763.0 ≤ v < 10.0.17763.689310.0.17763.0
Affected range stops below 10.0.17763.6893, so it looks safe — our inference, not a vendor statement
v < 10.0.19044.548710.0.19044.0 ≤ v < 10.0.19044.548710.0.19044.0
Affected range stops below 10.0.19044.5487, so it looks safe — our inference, not a vendor statement
v < 10.0.19045.548710.0.19045.0 ≤ v < 10.0.19045.548710.0.19045.0
Affected range stops below 10.0.19045.5487, so it looks safe — our inference, not a vendor statement
v < 10.0.22621.489010.0.22621.0 ≤ v < 10.0.22621.489010.0.22621.0
Affected range stops below 10.0.22621.4890, so it looks safe — our inference, not a vendor statement
v < 10.0.22631.489010.0.22631.0 ≤ v < 10.0.22631.489010.0.22631.0
Affected range stops below 10.0.22631.4890, so it looks safe — our inference, not a vendor statement
v < 10.0.26100.310710.0.26100.0 ≤ v < 10.0.26100.319410.0.26100.0
Affected range stops below 10.0.26100.3107, so it looks safe — our inference, not a vendor statement
Affected range stops below 10.0.26100.3194, so it looks safe — our inference, not a vendor statement
v < 10.0.14393.778510.0.14393.0 ≤ v < 10.0.14393.778510.0.14393.0
Affected range stops below 10.0.14393.7785, so it looks safe — our inference, not a vendor statement
v < 10.0.17763.689310.0.17763.0 ≤ v < 10.0.17763.689310.0.17763.0
Affected range stops below 10.0.17763.6893, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCActiveNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

7.1HIGHmicrosoft
Vector?

Quick Info

StatusANALYZED
CWE
CWE-59NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card