dbcve.org
Windows 10 1507Operating system · Microsoft

CVE-2025-32722

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
Improper access control in Windows Storage Port Driver 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

Improper access control in Windows Storage Port Driver allows a local authenticated attacker to read sensitive information they should not have access to. The vulnerability stems from insufficient authorization checks within the storage port driver component, enabling information disclosure to authorized but unprivileged local users.

MitigationApply the Microsoft security update for CVE-2025-32722 through standard Windows Update or enterprise patch management channels; verify storage 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. Check Windows version and build number
    Open Settings > System > About, or run 'winver' command, or run 'systeminfo' in Command Prompt and look at 'OS Version' line
    Affected if Build number is lower than the threshold for your Windows release: 10240.21034 (1507), 14393.8148 (1607), 17763.7434 (1809), 19044.5965 (21h2), 19045.5965 (22h2), 22621.5472 (11 22h2), 22631.5472 (11 23h2), or 26100.4270 (11 24h2)
  2. Verify Windows Update patch installation status
    Open Settings > Windows Update > Update history, or run 'wmic qfe list' in Command Prompt to list installed hotfixes
    Affected if No security update for CVE-2025-32722 is listed in the installed updates
  3. Confirm local authentication capability
    This vulnerability requires a local user account on the system. Verify if untrusted local accounts exist or if the system is used by multiple users
    Affected if Local non-administrator accounts are present and the system build is below the fixed version thresholds

The environment is affected if the Windows build number is below the version threshold for the installed Windows release and the system allows local user access.

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-32722 through standard Windows Update or enterprise patch management channels; verify storage functionality post-patch.

Recommended fix High confidence

Apply Microsoft security updates (Cumulative Update) for your specific Windows version to reach the fixed build number

  1. Identify the Windows version and build number by running `winver` or checking System Information
  2. Navigate to Windows Update Settings > Check for updates
  3. Apply the applicable Microsoft security update for CVE-2025-32722, which corresponds to the specific KB for your Windows version
  4. Alternatively, manually download and install the security update from the Microsoft Update Catalog for your specific Windows build (e.g., KB5012345 for your version)
  5. Restart the system after applying the update
  6. Verify the installed build matches or exceeds the fixed version: 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 risks apply (potential for compatibility issues with legacy software); back up critical data before updating

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
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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