dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-59199

HIGH · 7.8 CVSS v3.1 Published 2025-10-14
Fix available
A fix is available. Upgrade to 10.0.17763.7919 / 10.0.19044.6456 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
Improper access control in Software Protection Platform (SPP) 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 confidence

This is an improper access control vulnerability in Microsoft's Software Protection Platform (SPP) that allows an already authorized (but low-privilege) local attacker to elevate their privileges to higher levels on the system. The vulnerability stems from inadequate validation of access rights within the SPP component, which manages Windows activation and licensing.

MitigationApply the Microsoft security update addressing CVE-2025-59199 to patch the access control flaw in the Software Protection Platform. Verify that standard user accounts can no longer leverage the SPP to gain elevated privileges.

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.7919
Windows 10 21h2Operating system
Affected:< 10.0.19044.6456
Windows 10 22h2Operating system
Affected:< 10.0.19045.6456
Windows 11 22h2Operating system
Affected:< 10.0.22621.6060
Windows 11 23h2Operating system
Affected:< 10.0.22631.6060
Windows 11 24h2Operating system
Affected:< 10.0.26100.6899
Windows 11 25h2Operating system
Affected:< 10.0.26200.6899
Windows Server 2019Operating system
Affected:< 10.0.17763.7919

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 version and build number
    Run 'winver' from command prompt or execute 'Get-ComputerInfo | Select-Object OsName, OsVersion, WindowsVersion, OsBuildNumber' in PowerShell
    Affected if The build number falls below the safe thresholds: 17763.7919 (Win10 1809/Server 2019), 19044.6456 (Win10 21h2), 19045.6456 (Win10 22h2), 22621.6060 (Win11 22h2), 22631.6060 (Win11 23h2), 26100.6899 (Win11 24h2), or 26200.6899 (Win11 25h2)
  2. Verify Software Protection Platform service status
    Run 'Get-Service sppsvc' in PowerShell or check Services.msc for the 'Software Protection' service
    Affected if The SPP service (sppsvc) is present and running on the system, which is the default state for activated Windows installations
  3. Confirm current user privilege level
    Run 'whoami /groups' in Command Prompt or '$env:USERNAME' in PowerShell to identify the current user account
    Affected if The current user is a standard user (non-administrator) who has local access to the system, as the vulnerability exploits low-privilege authorized users gaining elevated access
  4. Check for unpatched SPP executable version
    Locate the SPP binary at C:\Windows\System32\sppsvc.exe, then right-click and view Properties > Details to see File Version, or run '(Get-Item C:\Windows\System32\sppsvc.exe).VersionInfo.FileVersion' in PowerShell
    Affected if The file version is older than the patched build numbers listed for your Windows version, indicating the patch has not been applied

A system is affected if it runs any of the vulnerable Windows versions listed AND has the SPP service enabled AND the security update for CVE-2025-59199 has not been installed.

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.7919 / 10.0.19044.6456 / 10.0.19045.6456 or later
Fixed in 10.0.17763.791910.0.19044.645610.0.19045.6456
Interim mitigation

Apply the Microsoft security update addressing CVE-2025-59199 to patch the access control flaw in the Software Protection Platform. Verify that standard user accounts can no longer leverage the SPP to gain elevated privileges.

Recommended fix High confidence

Windows 10 1809: 10.0.17763.7919 or later | Windows 10 21h2: 10.0.19044.6456 or later | Windows 10 22h2: 10.0.19045.6456 or later | Windows 11 22h2: 10.0.22621.6060 or later | Windows 11 23h2: 10.0.22631.6060 or later | Windows 11 24h2: 10.0.26100.6899 or later | Windows 11 25h2: 10.0.26200.6899 or

  1. Identify the current Windows build version by running 'winver' or 'systeminfo'
  2. Navigate to the Microsoft Security Response Center (msrc.microsoft.com) and search for CVE-2025-59199
  3. Download and install the applicable security update for your Windows version from the Microsoft Update Catalog
  4. Restart the system after applying the update
  5. Verify the installation by checking the installed updates list or confirming the build number matches or exceeds the fixed version for your release
Caveat Standard Windows security update - no breaking changes expected; apply during normal maintenance window

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

Fix this in Windows 10 1809 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-59199 — 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-59199 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