dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-33063

MEDIUM · 5.5 CVSS v3.1 Published 2025-06-10
Fix available
A fix is available. Upgrade to 10.0.14393.8148 / 10.0.17763.7434 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

This is an out-of-bounds read vulnerability in the Windows Storage Management Provider, a Windows component responsible for managing storage devices and volumes. The flaw allows a local, authorized (authenticated) attacker to read memory beyond intended boundaries, potentially exposing sensitive information from kernel memory. This is a local information disclosure vulnerability with low confidentiality impact.

MitigationApply the relevant Microsoft security patch when released. In the interim, restrict local access to trusted users only and monitor for unusual access patterns to the Windows Storage Management Provider.

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 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
Windows Server 2016Operating system
Affected:< 10.0.14393.8148
Windows Server 2019Operating system
Affected:< 10.0.17763.7434

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 version
    Open Command Prompt and run 'winver' or 'systeminfo | findstr "Build"' to obtain the full OS build number (for example, 19045.5965)
    Affected if The build number is lower than the fixed version for your specific Windows release as listed in the CVE affected versions
  2. Identify exact Windows release
    Run 'winver' to determine if you are on Windows 10 1809, 21h2, 22h2; Windows 11 22h2, 23h2, 24h2; Windows Server 2016 or Windows Server 2019
    Affected if Your Windows release matches any of the affected products listed in the CVE
  3. Compare against fixed version thresholds
    Consult the CVE affected versions list and compare: Windows 10 1809 must be >= 10.0.17763.7434, 21h2 >= 10.0.19044.5965, 22h2 >= 10.0.19045.5965; Windows 11 22h2 >= 10.0.22621.5472, 23h2 >= 10.0.22631.5472, 24h2 >= 10.0.26100.4270; Server 2016 >= 10.0.14393.8148; Server 2019 >= 10.0.17763.7434
    Affected if Your installed version is less than the required fixed version for your Windows release
  4. Confirm Storage Management Provider is present
    The Windows Storage Management Provider is a built-in Windows component for storage device management; verify it exists by checking for the 'StorageManagement' service or module in PowerShell with 'Get-Command *StorageManagement*' or via services.msc
    Affected if The Storage Management Provider component is present on the system and the OS version is vulnerable

A system is affected if it runs any Windows 10, Windows 11, or Windows Server version with a build number lower than the threshold specified for that release in the CVE, and the Storage Management Provider component is present.

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.14393.8148 / 10.0.17763.7434 / 10.0.19044.5965 or later
Fixed in 10.0.14393.814810.0.17763.743410.0.19044.5965
Interim mitigation

Apply the relevant Microsoft security patch when released. In the interim, restrict local access to trusted users only and monitor for unusual access patterns to the Windows Storage Management Provider.

Recommended fix High confidence

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 | Windows 11 23h2: build 10.0.22631.5472 | Windows 11 24h2: build 10.0.26100.4270 | Windows Server 2016: build 10.0.14393.8148 | Windows S

  1. Identify the current Windows version and build by running 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"'
  2. Open Settings > Windows Update (or WSUS for enterprise environments)
  3. Check for and install all pending Windows security updates
  4. Verify the update was applied by checking the build number matches or exceeds the fixed version for your Windows release
  5. Restart the system if prompted to complete the installation
Caveat Standard Windows update process with no expected service disruptions; typical update caveats apply (backup critical data before updating)

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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