dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2025-48000

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.14393.8246 / 10.0.17763.7558 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
Use after free 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 use-after-free vulnerability in the Windows Connected Devices Platform Service allows a local authenticated attacker to manipulate freed memory and elevate privileges to SYSTEM level. The Connected Devices Platform Service manages device discovery and communication for Windows.

MitigationApply Microsoft security updates for CVE-2025-48000 immediately. Prioritize workstations and servers with the Connected Devices Platform Service enabled. Limit local administrative access to essential personnel until patches are deployed.

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.8246
Windows 10 1809Operating system
Affected:< 10.0.17763.7558
Windows 10 21h2Operating system
Affected:< 10.0.19044.6093
Windows 10 22h2Operating system
Affected:< 10.0.19045.6093
Windows 11 22h2Operating system
Affected:< 10.0.22621.5624
Windows 11 23h2Operating system
Affected:< 10.0.22631.5624
Windows 11 24h2Operating system
Affected:< 10.0.26100.4652
Windows Server 2016Operating system
Affected:< 10.0.14393.8246

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 Name" /C:"OS Version"' and compare the build number to the listed threshold for your Windows release (e.g., 14393.8246 for Windows 10 1607/Server 2016, 17763.7558 for Windows 10 1809, etc.)
    Affected if The installed build number is lower than the threshold for your Windows version
  2. Identify the Connected Devices Platform Service
    Open Services (services.msc) and locate 'Connected Devices Platform Service' (CDPSvc) or run 'sc query CDPSvc'
    Affected if The service exists on the system (service name CDPSvc)
  3. Check if the service is enabled or running
    Run 'sc qc CDPSvc' to query the service configuration and 'sc query CDPSvc' to check its current state
    Affected if The service is set to start automatically or is currently running

You are affected if your Windows build is below the patched threshold AND the Connected Devices Platform Service (CDPSvc) is installed and enabled on your system.

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.8246 / 10.0.17763.7558 / 10.0.19044.6093 or later
Fixed in 10.0.14393.824610.0.17763.755810.0.19044.6093
Interim mitigation

Apply Microsoft security updates for CVE-2025-48000 immediately. Prioritize workstations and servers with the Connected Devices Platform Service enabled. Limit local administrative access to essential personnel until patches are deployed.

Recommended fix High confidence

Install the appropriate Windows cumulative security update containing the fix for CVE-2025-48000, targeting build numbers: 10.0.14393.8246 (Win 10 1607/Server 2016), 10.0.17763.7558 (Win 10 1809), 10.0.19044.6093 (Win 10 21h2), 10.0.19045.6093 (Win 10 22h2), 10.0.22621.5624 (Win 11 22h2), 10.0.22631

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine which Windows release (e.g., Windows 10 22h2, Windows 11 23h2, Windows Server 2016) is installed
  3. Open Windows Settings > Update & Security > Windows Update
  4. Click 'Check for updates' to download and install the latest cumulative update
  5. Alternatively, manually download the specific security update from the Microsoft Update Catalog matching your Windows version and build number
  6. Restart the computer when prompted to complete the installation
  7. Verify the update installed correctly by checking that the build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows update risks apply (potential for update-related issues; test in staging if possible)

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
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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