dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-54114

HIGH · 7.0 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 10.0.14393.8422 / 10.0.19044.6332 or later.
See remediation →
72/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
Concurrent execution using shared resource with improper synchronization ('race condition') in Windows Connected Devices Platform Service 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

A race condition vulnerability exists in the Windows Connected Devices Platform Service where improper synchronization of shared resources allows an authorized local attacker to elevate their privileges. The attacker exploits the timing window in the service's concurrent operations to gain higher-level system access.

MitigationApply Microsoft security updates for CVE-2025-54114 once available through Windows Update or WSUS. Verify that the Windows Connected Devices Platform Service is running with least-privilege principles and monitor for suspicious process behavior.

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.8422
Windows 10 21h2Operating system
Affected:< 10.0.19044.6332
Windows 10 22h2Operating system
Affected:< 10.0.19045.6332
Windows 11 22h2Operating system
Affected:< 10.0.22621.5909
Windows 11 23h2Operating system
Affected:< 10.0.22631.5909
Windows 11 24h2Operating system
Affected:< 10.0.26100.6508
Windows Server 2016Operating system
Affected:< 10.0.14393.8422
Windows Server 2022Operating system
Affected:< 10.0.20348.4106

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:H/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' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' from Command Prompt to obtain the exact Windows version and build number
    Affected if The installed build number falls below any of these thresholds: 14393.8422 (Win10 1607/Server 2016), 19044.6332 (Win10 21h2), 19045.6332 (Win10 22h2), 22621.5909 (Win11 22h2), 22631.5909 (Win11 23h2), 26100.6508 (Win11 24h2), or 20348.4106 (Server 2022)
  2. Verify Connected Devices Platform Service status
    Run 'sc query cdpsvc' or open Services.msc and locate 'Connected Devices Platform Service' (Cdpsvc) to check if it is running
    Affected if The service is running on an unpatched Windows version (see step 1) - the race condition exists in this service's concurrent operations
  3. Check service binary version
    Locate the service executable at %SystemRoot%\System32\CdSetup.dll or check the cdpsvc service binary via 'sc qc cdpsvc' and inspect the binary file version properties
    Affected if The binary version is older than the patched versions corresponding to the affected build ranges listed in step 1
  4. Review service ACL and permissions
    Run 'sc sdshow cdpsvc' to display the Security Descriptor Definition Language (SDDL) for the service and verify if low-privilege accounts have excessive service access
    Affected if Low-privilege users have permissions to interact with the cdpsvc service in a way that could trigger the race condition (improper synchronization of shared resources)
  5. Audit recent service-related events
    Open Event Viewer and check Windows Logs\System for Event ID 7045 (new service installed) or 7036 (service state change) related to cdpsvc, and look for unexpected child processes spawned from the service
    Affected if Unexpected service changes or child process spawns indicate potential exploitation activity targeting the race condition

You are affected if your Windows build number is below the thresholds listed for your Windows version AND the Connected Devices Platform Service is running.

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.8422 / 10.0.19044.6332 / 10.0.19045.6332 or later
Fixed in 10.0.14393.842210.0.19044.633210.0.19045.6332
Interim mitigation

Apply Microsoft security updates for CVE-2025-54114 once available through Windows Update or WSUS. Verify that the Windows Connected Devices Platform Service is running with least-privilege principles and monitor for suspicious process behavior.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.8422 | Windows 10 21h2: 10.0.19044.6332 | Windows 10 22h2: 10.0.19045.6332 | Windows 11 22h2: 10.0.22621.5909 | Windows 11 23h2: 10.0.22631.5909 | Windows 11 24h2: 10.0.26100.6508 | Windows Server 2016: 10.0.14393.8422 | Windows Server 2022: 10.0.20348.4106

  1. Open Settings > Update & Security > Windows Update and check for updates
  2. Install the latest Windows security updates that address this vulnerability (KB references can be found on the Microsoft Security Update Guide at msrc.microsoft.com)
  3. Restart the system when prompted to complete the installation
  4. Verify the update was installed by checking Windows Update history or running winver to confirm the build number matches or exceeds the fixed version for your product
Caveat Standard Windows update apply risk - updates may require restart and should be tested in staging environments before production deployment

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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