dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-55326

HIGH · 7.5 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 →
82/100
Remediation priority · High
Remotely reachable No privileges

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 Connected Devices Platform Service (Cdpsvc) allows an unauthorized attacker to execute code over a network.

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 exists in the Connected Devices Platform Service (Cdpsvc) where memory is accessed after it has been freed, allowing an unauthenticated remote attacker to achieve code execution over the network. The flaw stems from improper memory lifecycle management in the service.

MitigationApply vendor-provided security patches for Cdpsvc; until a patch is available, restrict network access to the service and monitor for indicators of compromise related to memory corruption exploitation.

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 Server 2019Operating system
Affected:< 10.0.17763.7919
Windows Server 2022Operating system
Affected:< 10.0.20348.4294

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

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/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. Verify Cdpsvc service exists
    Open Services console (services.msc) or run 'Get-Service -Name Cdpsvc' in PowerShell to confirm the Connected Devices Platform Service is present on the system
    Affected if The service exists on the system (all supported Windows versions listed in the CVE)
  2. Check if Cdpsvc is running
    Run 'Get-Service -Name Cdpsvc | Select-Object Status' in PowerShell or check the Status column in Services console
    Affected if Cdpsvc is currently running; the vulnerability only applies when the service is active
  3. Determine Windows build number
    Run 'winver' command or 'Get-ComputerInfo | Select-Object OsDisplayVersion, OsBuildNumber' in PowerShell to obtain the exact build version
    Affected if The installed build number falls below the fixed version for your Windows release (e.g., below 17763.7919 for Windows 10 1809/Server 2019, below 19044.6456 for Windows 10 21h2, below 19045.6456 for Windows 10 22h2, below 22621.6060 for Windows 11 22h2, below 22631.6060 for Windows 11 23h2, below 261
  4. Identify Windows release version
    Run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' or check the display version in winver to determine which Windows release (such as 1809, 21h2, 22h2, 22h2, 23h2, 24h2) is installed
    Affected if The system is running any of the affected Windows releases listed in the CVE with a build number below its corresponding fixed version

You are affected if Cdpsvc is running AND your Windows build number is below the fixed version for your specific Windows release as enumerated in the CVE.

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 vendor-provided security patches for Cdpsvc; until a patch is available, restrict network access to the service and monitor for indicators of compromise related to memory corruption exploitation.

Recommended fix High confidence

Install the applicable Windows security update containing the fix for CVE-2025-55326. The fixed builds are listed in step 4 - update to or beyond those build numbers.

  1. 1. Identify the current Windows build version by running 'winver' or 'systeminfo' in Command Prompt
  2. 2. Determine which Windows version and build you are running (e.g., Windows 10 22h2, Windows 11 23h2, Windows Server 2022)
  3. 3. Navigate to Windows Update settings or check Microsoft Update Catalog for available security updates
  4. 4. Install the latest Windows security updates. The fixed builds are: Windows 10 1809 (10.0.17763.7919+), Windows 10 21h2 (10.0.19044.6456+), Windows 10 22h2 (10.0.19045.6456+), Windows 11 22h2 (10.0.22621.6060+), Windows 11 23h2 (10.0.22631.6060+), Windows 11 24h2 (10.0.26100.6899+), Windows Server 2019 (10.0.17763.7919+), Windows Server 2022 (10.0.20348.4294+)
  5. 5. Restart the system after applying the updates
  6. 6. Verify the update was successful by checking the Windows build version again
Caveat Standard Windows update risks apply - ensure backups and test in non-production environments before deploying broadly

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

Fix this in Windows 10 1809 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,880
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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