dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-33060

MEDIUM · 5.5 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.10240.21034 / 10.0.14393.8148 or later.
See remediation →
57/100
Remediation priority · Elevated
Zero-click

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
Out-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 · high confidence

This is an out-of-bounds read vulnerability in Windows Storage Management Provider that allows a local, authorized attacker to read sensitive information beyond intended buffer boundaries. The vulnerability stems from improper bounds checking in the storage management component, leading to information disclosure without requiring code execution.

MitigationApply the relevant Microsoft Windows security update (KB) for CVE-2025-33060 through standard Windows Update or enterprise patch management deployment. Verify storage management functionality post-patch.

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.21034
Windows 10 1607Operating system
Affected:< 10.0.14393.8148
Windows 10 1809Operating system
Affected:< 10.0.17763.7434
Windows 10 21h2Operating system
Affected:< 10.0.19044.5965
Windows 10 22h2Operating system
Affected:< 10.0.19045.5965
Windows 11 22h2Operating system
Affected:< 10.0.22621.5472
Windows 11 23h2Operating system
Affected:< 10.0.22631.5472
Windows 11 24h2Operating system
Affected:< 10.0.26100.4270

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Retrieve Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the full version and build number
    Affected if The build number is lower than any of the following: 10.0.10240.21034 (1507), 10.0.14393.8148 (1607), 10.0.17763.7434 (1809), 10.0.19044.5965 (21h2), 10.0.19045.5965 (22h2), 10.0.22621.5472 (Win11 22h2), 10.0.22631.5472 (Win11 23h2), or 10.0.26100.4270 (Win11 24h2)
  2. Confirm Storage Management Provider component is present
    Verify the Windows Storage Management Provider service exists by running 'Get-Service -Name StorSvc' in PowerShell or checking the presence of storprov.dll in C:\Windows\System32
    Affected if The StorSvc service or storprov.dll file is present on the system, which is the default state for affected Windows versions

If the Windows build number is below the thresholds listed above and the Storage Management Provider component is present, the system is vulnerable to CVE-2025-33060.

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.21034 / 10.0.14393.8148 / 10.0.17763.7434 or later
Fixed in 10.0.10240.2103410.0.14393.814810.0.17763.7434
Interim mitigation

Apply the relevant Microsoft Windows security update (KB) for CVE-2025-33060 through standard Windows Update or enterprise patch management deployment. Verify storage management functionality post-patch.

Recommended fix High confidence

Install the appropriate Windows security update for your version reaching the specified build number (e.g., Windows 10 22h2 build 10.0.19045.5965 or later)

  1. Check current Windows build version by running 'winver' or 'systeminfo | findstr /B /C:"OS Version"'
  2. Open Windows Update by pressing Windows key and searching for 'Windows Update'
  3. Click 'Check for updates' and allow Windows to scan for available updates
  4. Install all pending updates, particularly any security updates for Windows Storage Management Provider
  5. Restart the system if prompted to complete the installation
  6. Verify the installed build version matches or exceeds the fixed version for your Windows release: Windows 10 1507: 10.0.10240.21034, Windows 10 1607: 10.0.14393.8148, Windows 10 1809: 10.0.17763.7434, Windows 10 21h2: 10.0.19044.5965, Windows 10 22h2: 10.0.19045.5965, Windows 11 22h2: 10.0.22621.5472, Windows 11 23h2: 10.0.22631.5472, Windows 11 24h2: 10.0.26100.4270
Caveat Standard Windows security patching carries minimal risk; verify critical applications function normally after update

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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