dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-59512

HIGH · 7.8 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 10.0.14393.8594 / 10.0.17763.8027 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 Customer Experience Improvement Program (CEIP) 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

Improper access control in the Customer Experience Improvement Program (CEIP) component allows a locally authenticated attacker with basic authorized access to escalate privileges to higher levels. The vulnerability stems from missing or insufficient permission validation within the CEIP service that can be bypassed locally.

MitigationImplement proper authorization checks and enforce least-privilege access controls in the CEIP component to prevent unauthorized privilege escalation. Apply vendor-provided patches or updates to the CEIP service.

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 1607Operating system
Affected:< 10.0.14393.8594
Windows 10 1809Operating system
Affected:< 10.0.17763.8027
Windows 10 21h2Operating system
Affected:< 10.0.19044.6575
Windows 10 22h2Operating system
Affected:< 10.0.19045.6575
Windows 11 23h2Operating system
Affected:< 10.0.22631.6199
Windows 11 24h2Operating system
Affected:< 10.0.26100.7092
Windows 11 25h2Operating system
Affected:< 10.0.26200.7092
Windows Server 2012Operating system
Affected:all versions= r2

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. Check Windows version against affected ranges
    Run 'winver' or 'systeminfo | findstr /B /C:"OS"' to obtain the installed Windows version and build number. Compare the build number to the affected version thresholds: 14393.8594 (1607), 17763.8027 (1809), 19044.6575 (21h2), 19045.6575 (22h2), 22631.6199 (23h2), 26100.7092 (24h2), 26200.7092 (25h2), or verify if the system is Windows Server 2012 R2.
    Affected if The installed build number is lower than the threshold for the corresponding Windows version, or the system is Windows Server 2012 R2.
  2. Verify CEIP service presence
    Run 'sc query CEIP' or check the 'Customer Experience Improvement Program' (CEIP) service status in Services.msc. Also check the registry key 'HKLM\SOFTWARE\Policies\Microsoft\SQMClient\Windows\CEIPEnable' if it exists.
    Affected if The CEIP service exists and is present on the system (the vulnerability exists in the CEIP component itself).
  3. Confirm local authentication context
    Verify the current user context using 'whoami /all' and check for standard user or basic authorized account membership. This vulnerability requires a locally authenticated attacker with basic authorized access.
    Affected if The system has user accounts with standard or basic authorization (non-admin) that can log on locally, as the flaw allows such accounts to escalate privileges through CEIP.

The system is affected if it runs a Windows version or build lower than the thresholds listed AND has the CEIP component present with locally authenticated standard users.

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.14393.8594 / 10.0.17763.8027 / 10.0.19044.6575 or later
Fixed in 10.0.14393.859410.0.17763.802710.0.19044.6575
Interim mitigation

Implement proper authorization checks and enforce least-privilege access controls in the CEIP component to prevent unauthorized privilege escalation. Apply vendor-provided patches or updates to the CEIP service.

Recommended fix High confidence

Windows 10 1607: build 10.0.14393.8594 | Windows 10 1809: build 10.0.17763.8027 | Windows 10 21h2: build 10.0.19044.6575 | Windows 10 22h2: build 10.0.19045.6575 | Windows 11 23h2: build 10.0.22631.6199 | Windows 11 24h2: build 10.0.26100.7092 | Windows 11 25h2: build 10.0.26200.7092 | Windows Serve

  1. Verify current Windows build version by running `winver` or `systeminfo` in Command Prompt
  2. Deploy the appropriate Windows Security Update for your version via Windows Update or your patch management system
  3. For Windows Server 2012/R2: Microsoft no longer supports these versions; migrate to a supported Windows Server version (2016 or later)
  4. After applying the update, confirm successful installation by checking Windows Update history
  5. Reboot the system as required to complete the update installation
  6. Verify the fixed build version matches or exceeds: Windows 10 1607: 10.0.14393.8594 | Windows 10 1809: 10.0.17763.8027 | Windows 10 21h2: 10.0.19044.6575 | Windows 10 22h2: 10.0.19045.6575 | Windows 11 23h2: 10.0.22631.6199 | Windows 11 24h2: 10.0.26100.7092 | Windows 11 25h2: 10.0.26200.7092
Caveat Windows Server 2012/R2 has reached end of support; migrating to a newer server version may require application compatibility testing

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

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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