dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-33058

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

An out-of-bounds read vulnerability in Windows Storage Management Provider allows a local, authorized attacker to read sensitive information beyond intended buffer boundaries due to improper bounds checking.

MitigationApply the latest Microsoft security updates for Windows to patch the Windows Storage Management Provider component.

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. Check Windows build number
    Run 'winver' or 'systeminfo' in Command Prompt, or use PowerShell: Get-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion' | Select-Object CurrentBuild, DisplayVersion, UBR
    Affected if The build number is lower than the threshold for your Windows release (10.0.10240.21034 for 1507, 10.0.14393.8148 for 1607, 10.0.17763.7434 for 1809, 10.0.19044.5965 for 21h2, 10.0.19045.5965 for 22h2, 10.0.22621.5472 for Win11 22h2, 10.0.22631.5472 for Win11 23h2, 10.0.26100.4270 for Win11 24h2)
  2. Identify Windows release version
    Run 'winver' to determine if you are on Windows 10 1507, 1607, 1809, 21h2, 22h2 or Windows 11 22h2, 23h2, 24h2
    Affected if Your specific Windows release version falls within the affected version ranges and the build number is below the corresponding patch threshold
  3. Confirm Storage Management Provider presence
    Check for the Storage Management Provider service via PowerShell: Get-Service -Name 'StorSvc' or check for the feature in Windows Features. The provider is implemented as part of the Windows Storage subsystem.
    Affected if The StorSvc service exists and is running on the system, indicating the vulnerable component is present

You are affected if your Windows build number is lower than the patch threshold for your specific Windows release and the Windows Storage Management Provider component is present on your system.

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 latest Microsoft security updates for Windows to patch the Windows Storage Management Provider component.

Recommended fix High confidence

Apply the May 2025 Windows Security Updates (KB5xxxxx) or later from Windows Update/Microsoft Update Catalog for your specific Windows version

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which version bracket your system falls into from the affected versions list
  3. Apply the latest Windows Security Update from Windows Update that corresponds to your version
  4. Verify the update installed successfully by checking Windows Update history
  5. Confirm the version matches or exceeds the fixed threshold: 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 update with no special configuration changes required; ensure backups and system recovery options are available before applying

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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