CVE-2025-59192
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 · uneditedBuffer over-read in Storport.sys Driver allows an authorized attacker to elevate privileges 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 confidenceA buffer over-read vulnerability exists in Storport.sys, a Windows kernel-mode driver responsible for storage port miniport drivers. The flaw allows a local authenticated attacker to read beyond allocated memory boundaries, which can be leveraged to elevate privileges from a standard user account to SYSTEM-level 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< 10.0.10240.21161< 10.0.14393.8519< 10.0.17763.7919< 10.0.19044.6456< 10.0.19045.6456< 10.0.22621.6060<= 10.0.22631.6060< 10.0.26100.6899CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Locate the Storport.sys driver fileOpen File Explorer and navigate to C:\Windows\System32\drivers\Storport.sys, or run 'driverquery /v /fo list' and look for Storport.sys in the listAffected if The file does not exist (but note: Storport.sys is a core Windows driver and should be present on systems using storage miniport drivers)
-
Check the version of Storport.sysRight-click Storport.sys, select Properties, go to the Details tab, and note the File Version value. Alternatively, run 'powershell (Get-Item C:\Windows\System32\drivers\Storport.sys).VersionInfo'Affected if The displayed version is lower than the version in the security update for this CVE (version comparison needed against patched driver)
-
Identify the Windows version and buildRun 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the exact Windows 10 or 11 build numberAffected if The Windows build falls within any of the affected ranges: 10.0.10240.21161 or lower for 1507, 10.0.14393.8519 or lower for 1607, 10.0.17763.7919 or lower for 1809, 10.0.19044.6456 or lower for 21h2, 10.0.19045.6456 or lower for 22h2, 10.0.22621.6060 or lower for 11 22h2, 10.0.22631.6060 or lower fo
-
Confirm the local attacker vector applicabilityVerify that non-administrative user accounts exist on the system, as the vulnerability requires a local authenticated user to exploit the buffer over-readAffected if Standard user accounts are present and the system is running a vulnerable Windows version
A system is affected if it runs Windows 10 1507 through 22h2, or Windows 11 22h2 through 24h2, with build numbers below the thresholds listed and has non-administrative user accounts present.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.10240.2116110.0.14393.851910.0.17763.7919
Apply the latest Windows security updates that include the Storport.sys patch. Until patching is possible, minimize local privileged access and monitor for suspicious use of storage diagnostic tools.
Install the latest Windows cumulative security update that includes the fix for CVE-2025-59192, targeting specific builds: Windows 10 1507 to 10.0.10240.21161, Windows 10 1607 to 10.0.14393.8519, Windows 10 1809 to 10.0.17763.7919, Windows 10 21h2 to 10.0.19044.6456, Windows 10 22h2 to 10.0.19045.64
- Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
- Determine which build version is currently installed (e.g., 10.0.19045.xxxx)
- Navigate to Windows Update via Settings > Update & Security > Windows Update
- Check for updates and install the latest cumulative security update, or manually download the specific KB patch for your Windows version from the Microsoft Update Catalog
- After installation, verify the new build version matches or exceeds the fixed version for your Windows release (e.g., Windows 10 22h2 should be >= 10.0.19045.6456)
- Restart the system as prompted to complete the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-59192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-59192 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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