dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-53721

HIGH · 7.0 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 10.0.17763.7678 / 10.0.19044.6216 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
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 Windows Connected Devices Platform Service allows a locally authorized attacker to manipulate freed memory and elevate privileges to higher integrity levels. The vulnerability stems from improper memory management in the service's handling of device connections.

MitigationApply the Microsoft security update for CVE-2025-53721 when released. Prioritize testing in environments with Windows Connected Devices Platform Service enabled due to potential service dependencies.

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.7678
Windows 10 21h2Operating system
Affected:< 10.0.19044.6216
Windows 10 22h2Operating system
Affected:< 10.0.19045.6216
Windows 11 22h2Operating system
Affected:< 10.0.22621.5768
Windows 11 23h2Operating system
Affected:< 10.0.22631.5768
Windows 11 24h2Operating system
Affected:< 10.0.26100.4851
Windows Server 2019Operating system
Affected:< 10.0.17763.7678
Windows Server 2022Operating system
Affected:< 10.0.20348.3989

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. Verify Windows Connected Devices Platform Service is enabled
    Open Services (services.msc) or run 'Get-Service | Where-Object {$_.DisplayName -like "*Connected*Devices*"}' in PowerShell to find if the Windows Connected Devices Platform Service is installed and running
    Affected if The service is present and running - the vulnerability requires this service to be enabled for exploitation
  2. Check installed Windows build version
    Run 'winver' or execute 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to view the current Windows build number, or query the registry at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion for CurrentBuild and DisplayVersion values
    Affected if The build number falls below the fixed version for your Windows release (e.g., Windows 10 1809 below 17763.7678, Windows 11 24h2 below 26100.4851)
  3. Confirm specific Windows release and architecture
    Run 'msinfo32' or check System Properties to identify exact Windows edition (Home/Pro/Enterprise) and release version (such as 1809, 21h2, 22h2 for Windows 10, or 22h2/23h2/24h2 for Windows 11)
    Affected if Running a vulnerable Windows release that matches the affected version ranges provided in the CVE advisory
  4. Verify Windows Server version if applicable
    If running Windows Server, run 'systeminfo' or check the registry at HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion to determine the exact Windows Server version and build number
    Affected if Running Windows Server 2019 below build 17763.7678 or Windows Server 2022 below build 20348.3989

You are affected if the Windows Connected Devices Platform Service is enabled and your Windows build version is lower than the fixed version for your specific Windows release as listed in the CVE affected products table.

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.7678 / 10.0.19044.6216 / 10.0.19045.6216 or later
Fixed in 10.0.17763.767810.0.19044.621610.0.19045.6216
Interim mitigation

Apply the Microsoft security update for CVE-2025-53721 when released. Prioritize testing in environments with Windows Connected Devices Platform Service enabled due to potential service dependencies.

Recommended fix High confidence

Windows 10 1809: 10.0.17763.7678 | Windows 10 21h2: 10.0.19044.6216 | Windows 10 22h2: 10.0.19045.6216 | Windows 11 22h2: 10.0.22621.5768 | Windows 11 23h2: 10.0.22631.5768 | Windows 11 24h2: 10.0.26100.4851 | Windows Server 2019: 10.0.17763.7678 | Windows Server 2022: 10.0.20348.3989 or later

  1. Open Windows Settings and navigate to Update & Security > Windows Update
  2. Click 'Check for updates' to download and install the latest cumulative security update
  3. Restart the system when prompted to complete the patch installation
  4. Verify the installed KB update includes the fix for CVE-2025-53721 by checking the update history
Caveat Standard Windows security update; may require restart

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
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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