dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-33065

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 exists in Windows Storage Management Provider that allows a local, authorized attacker to read sensitive information from memory beyond intended buffer boundaries.

MitigationApply the Microsoft security update for CVE-2025-33065 once released. Prioritize patching systems with direct access to sensitive data or where local attacker access is plausible.

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. Determine Windows version and build number
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact Windows version and build number
    Affected if The build number is lower than the fixed version for your Windows release (e.g., below 10.0.19045.5965 for Windows 10 22h2)
  2. Identify Windows release version
    Run 'winver' to confirm whether you are on Windows 10 1507, 1607, 1809, 21h2, 22h2, or Windows 11 22h2, 23h2, or 24h2
    Affected if You are running any of the listed Windows 10 or Windows 11 releases and your specific build falls below the corresponding fixed version
  3. Confirm Storage Management Provider component is present
    Check for the presence of the Storage Management Provider by running 'Get-Process' or looking for 'storagemgmt' related services via 'Get-Service | Where-Object {$_.Name -like "*Storage*"}'
    Affected if The Storage Management Provider component is installed on the system (which is default on affected Windows versions)
  4. Compare installed build to CVE threshold
    Run 'ver' command at command prompt or check the build via 'winver' and compare numerically against the affected version ranges listed in the CVE
    Affected if Your installed build number is less than the threshold for your specific Windows release as specified in the affected products list

You are affected if your Windows version and build number fall within any of the affected ranges listed and the 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 Microsoft security update for CVE-2025-33065 once released. Prioritize patching systems with direct access to sensitive data or where local attacker access is plausible.

Recommended fix High confidence

Upgrade to the specific cumulative update containing the fix: Windows 10 1507 build 10.0.10240.21034, Windows 10 1607 build 10.0.14393.8148, Windows 10 1809 build 10.0.17763.7434, Windows 10 21h2 build 10.0.19044.5965, Windows 10 22h2 build 10.0.19045.5965, Windows 11 22h2 build 10.0.22621.5472, Win

  1. Open Windows Settings and navigate to Windows Update
  2. Check for updates and install all available cumulative updates
  3. Verify the installed version matches or exceeds the fixed build number for your Windows version: Windows 10 1507 should be 10.0.10240.21034 or higher; Windows 10 1607 should be 10.0.14393.8148 or higher; Windows 10 1809 should be 10.0.17763.7434 or higher; Windows 10 21h2 should be 10.0.19044.5965 or higher; Windows 10 22h2 should be 10.0.19045.5965 or higher; Windows 11 22h2 should be 10.0.22621.
  4. Restart the system after applying updates
Caveat Standard Windows update apply risks - ensure backups exist before major updates; some enterprise environments may require IT approval

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

Fix this in Windows 10 1507 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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