dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-59516

HIGH · 7.8 CVSS v3.1 Published 2025-12-09
Fix available
A fix is available. Upgrade to 10.0.17763.8146 / 10.0.19044.6691 or later.
See remediation →
80/100
Remediation priority · High
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
Missing authentication for critical function in Windows Storage VSP 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 · high confidence

A missing authentication check in the Windows Storage VSP (Virtual Service Provider) Driver allows a locally authenticated attacker to call a critical function without proper authorization, enabling local privilege escalation to SYSTEM or administrator privileges.

MitigationApply the Microsoft security update for CVE-2025-59516 through Windows Update or enterprise patch management to remediate the missing authentication in the Storage VSP Driver.

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.8146
Windows 10 21h2Operating system
Affected:< 10.0.19044.6691
Windows 10 22h2Operating system
Affected:< 10.0.19045.6691
Windows 11 23h2Operating system
Affected:< 10.0.22631.6345
Windows 11 24h2Operating system
Affected:< 10.0.26100.7392
Windows 11 25h2Operating system
Affected:< 10.0.26200.7392
Windows Server 2019Operating system
Affected:< 10.0.17763.8146
Windows Server 2022Operating system
Affected:< 10.0.20348.4467

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to display the installed Windows build number
    Affected if The build number is lower than the threshold for your Windows version (17763.8146 for 1809/Server 2019, 19044.6691 for 21h2, 19045.6691 for 22h2, 22631.6345 for 11 23h2, 26100.7392 for 11 24h2, 26200.7392 for 11 25h2, or 20348.4467 for Server 2022)
  2. Query exact OS build via registry
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' and '/v UBR' to get the full build number (combine them for the complete version like 10.0.XXXXX.XXXX)
    Affected if The combined build number is below the affected version threshold for your Windows release
  3. Check Storage VSP driver presence
    Run 'sc query storvsp' or check for the driver file at %SystemRoot%\System32\drivers\storvsp.sys using 'dir %SystemRoot%\System32\drivers\storvsp.sys'
    Affected if The driver file exists on the system (the vulnerability exists in this driver, though detection requires comparing build versions)

You are affected if your Windows build number is below the specific threshold for your Windows version as listed in the affected versions range.

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.17763.8146 / 10.0.19044.6691 / 10.0.19045.6691 or later
Fixed in 10.0.17763.814610.0.19044.669110.0.19045.6691
Interim mitigation

Apply the Microsoft security update for CVE-2025-59516 through Windows Update or enterprise patch management to remediate the missing authentication in the Storage VSP Driver.

Recommended fix High confidence

Apply KB5066666 (or subsequent security updates for this CVE) to reach the minimum fixed build for your Windows version (17763.8146, 19044.6691, 19045.6691, 22631.6345, 26100.7392, 26200.7392, or 20348.4467 depending on version)

  1. 1. Apply the security update for CVE-2025-59516 from Microsoft Update Catalog or Windows Update
  2. 2. For Windows 10 systems: Navigate to Settings > Update & Security > Windows Update and check for updates
  3. 3. For Windows 11 systems: Navigate to Settings > Windows Update and check for updates
  4. 4. For Windows Server systems: Use Windows Update for Business, WSUS, or manually download updates from Microsoft Update Catalog
  5. 5. Restart the system after applying the update
  6. 6. Verify the update was installed by checking the installed updates list or running: winver (to confirm build number matches or exceeds the fixed version)
Caveat Standard Windows security update with no expected breaking changes; as a local privilege escalation fix, this patch should be prioritized

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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