dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-33061

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

This is an out-of-bounds read vulnerability in Windows Storage Management Provider. A local authenticated attacker can exploit this to read memory beyond intended buffer boundaries, potentially exposing sensitive system information. The vulnerability is classified as an information disclosure issue with CVSS 5.5.

MitigationApply the appropriate Microsoft security update for this vulnerability through Windows Update or the Microsoft Security Update Guide. Prioritize patching systems with local user access.

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

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 version and build number
    Run 'winver' from the command line or check 'systeminfo' and locate the 'OS Version' line. Note the full build number (e.g., 10.0.19045.5965).
    Affected if The build number is lower than the threshold for your Windows edition as listed in the affected versions.
  2. Identify Windows edition family
    Run 'winver' or check 'systeminfo' to determine if the system is Windows 10, Windows 11, or Windows Server 2016, and note the specific release (such as 1607, 1809, 21h2, 22h2, 23h2, 24h2).
    Affected if The system is any of the Windows 10 releases (1607, 1809, 21h2, 22h2), Windows 11 releases (22h2, 23h2, 24h2), or Windows Server 2016 listed in the affected versions.
  3. Verify Storage Management Provider component
    Check if the Windows Storage Management Provider is available by running 'Get-WindowsOptionalFeature -Online -FeatureName *Storage*' in PowerShell or reviewing installed Windows features.
    Affected if The Storage Management Provider feature is present on the system (this component must exist for the vulnerability to be exploitable).
  4. Compare build to affected thresholds
    Compare your detected build number against these thresholds: Windows 10 1607/Server 2016: 14393.8148; Windows 10 1809: 17763.7434; Windows 10 21h2: 19044.5965; Windows 10 22h2: 19045.5965; Windows 11 22h2: 22621.5472; Windows 11 23h2: 22631.5472; Windows 11 24h2: 26100.4270.
    Affected if Your installed build number is less than the corresponding threshold for your Windows edition and release.

A system is affected if it runs a Windows 10, Windows 11, or Windows Server 2016 version with a build number lower than the threshold listed for that specific release, 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 appropriate Microsoft security update for this vulnerability through Windows Update or the Microsoft Security Update Guide. Prioritize patching systems with local user access.

Recommended fix High confidence

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 | Windows Server 2016: 10.0.14393.8148

  1. Identify the current Windows version and build number using `winver` or `systeminfo`
  2. Navigate to Windows Update Settings > Check for updates
  3. Install the latest cumulative security update for your specific Windows version
  4. Alternatively, manually download and install the appropriate security update from the Microsoft Update Catalog by searching for the KB number corresponding to CVE-2025-33061
  5. After installation, restart the system to apply the update
  6. Verify the fix by checking that the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows cumulative update risks; ensure backups and test in non-production environment first

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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