CVE-2025-33055
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 confidenceAn out-of-bounds read vulnerability in Windows Storage Management Provider allows a locally authenticated, authorized attacker to read sensitive information beyond intended memory boundaries. The flaw enables information disclosure without requiring elevated privileges.
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.14393.8148< 10.0.17763.7434< 10.0.19044.5965< 10.0.19045.5965< 10.0.22621.5472< 10.0.22631.5472< 10.0.26100.4270CVSS 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.
-
Check Windows build versionRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the installed Windows build numberAffected if The build number falls below any of these thresholds: 10240.21034 (1507), 14393.8148 (1607), 17763.7434 (1809), 19044.5965 (21h2), 19045.5965 (22h2), 22621.5472 (22h2), 22631.5472 (23h2), 26100.4270 (24h2)
-
Verify Storage Management Provider component is presentCheck for the presence of 'StorageManagement' provider by running 'Get-StorageProvider' in PowerShell or checking for 'StorageManagement.dll' in System32 folderAffected if The Storage Management Provider component exists on the system and the Windows version is in the affected range above
-
Confirm local authentication contextReview system logs and audit local user accounts to confirm standard user authentication is possible on the endpointAffected if Local user authentication is enabled and the Windows version is vulnerable as determined by step 1
A system is affected if it runs any Windows 10 or 11 version with a build number lower than the thresholds listed and has the Windows Storage Management Provider component present.
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
Deploy Microsoft security updates for Windows when released. Verify that Windows Storage Management Provider functions normally after patching.
Apply May 2025 Windows Security Updates (KB5055527 or subsequent) to reach the fixed build numbers for each affected version
- Identify the current Windows build version by running 'winver' or 'systeminfo | findstr /B /C:"OS Version"'
- Determine which Windows 10 or 11 version/branch is running (1507, 1607, 1809, 21h2, 22h2, 22h2, 23h2, or 24h2)
- Apply the appropriate Windows Update to reach the fixed build: Windows 10 1507 to build 10.0.10240.21034 or later, Windows 10 1607 to build 10.0.14393.8148 or later, Windows 10 1809 to build 10.0.17763.7434 or later, Windows 10 21h2 to build 10.0.19044.5965 or later, Windows 10 22h2 to build 10.0.19045.5965 or later, Windows 11 22h2 to build 10.0.22621.5472 or later, Windows 11 23h2 to build 10.0.
- Verify the update was applied successfully by checking the build number again after restarting
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-33055 — 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-33055 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