dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2025-53156

MEDIUM · 5.5 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.25398.1791 / 10.0.26100.4851 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
Exposure of sensitive information to an unauthorized actor in 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

A local authorization bypass in a Storage Port Driver allows an authenticated local attacker to access sensitive information that should be protected. The vulnerability stems from improper access controls within the kernel-mode storage driver component.

MitigationApply the vendor-supplied patch or updated driver for the affected Storage Port Driver. For Microsoft drivers, this typically comes through Windows Update; for third-party drivers, obtain the updated driver from the hardware vendor.

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 11 24h2Operating system
Affected:< 10.0.26100.4851
Windows Server 2022 23h2Operating system
Affected:< 10.0.25398.1791
Windows Server 2025Operating system
Affected:< 10.0.26100.4851

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 | findstr /B /C:"OS Version"' to see the full build number
    Affected if The build number is below 10.0.26100.4851 for Windows 11 24h2 or Windows Server 2025, or below 10.0.25398.1791 for Windows Server 2022 23h2
  2. Confirm Windows version and release
    Run 'winver' to verify exact Windows edition and release (24h2 or 23h2)
    Affected if Running an affected version (Windows 11 24h2, Windows Server 2022 23h2, or Windows Server 2025) with a build number below the fixed threshold
  3. Identify Storage Port Driver version
    Open Device Manager, expand 'Storage controllers', right-click the storage controller, select Properties, then go to the Driver tab to view driver version and date
    Affected if The Storage Port Driver version is older than the version bundled with the patched build (10.0.26100.4851 or 10.0.25398.1791)
  4. Check for suspicious storage driver behavior
    Review Windows Event Viewer under 'Application and Services Logs > Microsoft > Windows > Storage' for anomalous access events from unexpected user contexts
    Affected if Unexpected local authenticated access attempts to storage driver functions appear in logs

You are affected if you are running Windows 11 24h2, Windows Server 2022 23h2, or Windows Server 2025 with a build number lower than the fixed versions, AND the Storage Port Driver has not been updated to the patched version.

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.25398.1791 / 10.0.26100.4851 or later
Fixed in 10.0.25398.179110.0.26100.4851
Interim mitigation

Apply the vendor-supplied patch or updated driver for the affected Storage Port Driver. For Microsoft drivers, this typically comes through Windows Update; for third-party drivers, obtain the updated driver from the hardware vendor.

Recommended fix Moderate confidence

Windows 11 24h2: version 10.0.26100.4851 or later | Windows Server 2022 23h2: version 10.0.25398.1791 or later | Windows Server 2025: version 10.0.26100.4851 or later

  1. Open Settings > Windows Update on the affected system
  2. Check for updates and install all available updates
  3. Verify the installed version by running 'winver' or 'systeminfo' from command prompt
  4. Confirm the version meets or exceeds: 10.0.26100.4851 for Windows 11 24h2/Windows Server 2025, or 10.0.25398.1791 for Windows Server 2022 23h2
Caveat Standard Windows update process; ensure backups of critical data exist before applying updates

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

Fix this in Windows 11 24h2 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
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,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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