CVE-2025-24065
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 · uneditedOut-of-bounds read in Windows Storage Management Provider allows an authorized attacker to disclose information 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 an out-of-bounds read vulnerability in the Windows Storage Management Provider. An authorized local attacker with low privileges can exploit improper memory boundary checks to read information beyond allocated buffers, potentially exposing sensitive data from memory.
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.10240.21034< 10.0.19045.5965< 10.0.22621.5472< 10.0.22631.5472< 10.0.26100.4270< 10.0.14393.8148< 10.0.17763.7434< 10.0.20348.3745CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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.
-
Retrieve Windows version and build numberOpen Command Prompt or PowerShell and run: `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` to obtain the exact Windows version and build number.Affected if The displayed version is lower than any of the following: Windows 10 1507 build 10240.21034, Windows 10 22h2 build 19045.5965, Windows 11 22h2 build 22621.5472, Windows 11 23h2 build 22631.5472, Windows 11 24h2 build 26100.4270, Windows Server 2016 build 14393.8148, Windows Server 2019 build 17763.7
-
Confirm Storage Management Provider component is presentCheck for the presence of the Storage Management Provider by querying the Windows feature list. In PowerShell, run: `Get-WindowsOptionalFeature -Online | Where-Object {$_.FeatureName -like "*Storage*"}` or check for the service: `Get-Service | Where-Object {$_.DisplayName -like "*Storage*"}`.Affected if The Storage Management Provider feature or service is found and the Windows version is within the affected ranges listed above.
-
Verify current user context and privilegesIn PowerShell, run: `whoami /priv` to list current user privileges. The vulnerability notes exploitation by an authorized local attacker with low privileges.Affected if The system is unpatched and the current user account has local access, regardless of privilege level, as the flaw can be exploited by low-privilege users.
A system is affected if it runs any of the Windows versions or Windows Server versions listed above and contains the Storage Management Provider component; the primary indicator is an unpatched Windows version lower than the specified build numbers.
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.10240.2103410.0.14393.814810.0.17763.7434
Apply the relevant Microsoft security update for this vulnerability. Until a patch is available, limit local user privileges and restrict access to sensitive systems following least-privilege principles.
KB5055523 or subsequent security updates for each affected Windows version (10.0.10240.21034, 10.0.19045.5965, 10.0.22621.5472, 10.0.22631.5472, 10.0.26100.4270, 10.0.14393.8148, 10.0.17763.7434, 10.0.20348.3745)
- Identify the installed Windows version and build number (winver or systeminfo)
- Locate the corresponding security update for CVE-2025-24065 from the Microsoft Security Response Center (msrc.microsoft.com)
- Apply the security update via Windows Update, or download and install the specific KB from the Microsoft Update Catalog
- Restart the system as prompted to complete the patch installation
- Verify the installed build matches or exceeds the fixed version for your Windows release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-24065 — 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-2025-24065 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