dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2025-49724

HIGH · 8.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 10.0.17763.7558 / 10.0.19044.6093 or later.
See remediation →
95/100
Remediation priority · Urgent
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 Windows Connected Devices Platform Service 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 Windows Connected Devices Platform Service. This memory corruption flaw allows an unauthenticated attacker to achieve remote code execution by exploiting the dangling pointer condition after memory is freed.

MitigationApply Microsoft security updates for Windows Connected Devices Platform Service when released. Prioritize internet-facing systems given the network-exploitable nature of this vulnerability.

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.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 2019Operating system
Affected:< 10.0.17763.7558
Windows Server 2022Operating system
Affected:< 10.0.20348.3932

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

CVSS:3.1/AV:N/AC:L/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. Identify Windows version and build number
    Open Command Prompt or PowerShell and run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to see the installed Windows build
    Affected if The build number is lower than any of the following: 17763.7558, 19044.6093, 19045.6093, 22621.5624, 22631.5624, 26100.4652, or 20348.3932 depending on your Windows edition and version
  2. Verify Windows 10 build number
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' in Command Prompt to get the exact build
    Affected if For Windows 10 1809 (build 17763), the build is below 7558; for 21h2 (build 19044), below 6093; for 22h2 (build 19045), below 6093
  3. Verify Windows 11 build number
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' in Command Prompt to get the exact build
    Affected if For Windows 11 22h2 (build 22621), the build is below 5624; for 23h2 (build 22631), below 5624; for 24h2 (build 26100), below 4652
  4. Verify Windows Server build number
    Run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' in Command Prompt to get the exact build
    Affected if For Windows Server 2019 (build 17763), the build is below 7558; for Windows Server 2022 (build 20348), below 3932
  5. Check if Connected Devices Platform Service exists and is running
    Open Services console (services.msc) and look for 'Connected Devices Platform Service' (CDPSvc) or run 'sc query cdpsvc' in Command Prompt
    Affected if The service exists and is running on a vulnerable Windows version as identified in the build checks above

You are affected if your Windows build number falls below the threshold for your specific Windows edition and version as listed in the affected products, and the Connected Devices Platform Service is present 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.17763.7558 / 10.0.19044.6093 / 10.0.19045.6093 or later
Fixed in 10.0.17763.755810.0.19044.609310.0.19045.6093
Interim mitigation

Apply Microsoft security updates for Windows Connected Devices Platform Service when released. Prioritize internet-facing systems given the network-exploitable nature of this vulnerability.

Recommended fix High confidence

Apply the Windows Security Update for May 2025 (or subsequent relevant patch) that includes CVE-2025-49724, targeting the specific fixed build for your Windows version: 10.0.17763.7558 (1809/Server 2019), 10.0.19044.6093 (21h2), 10.0.19045.6093 (22h2), 10.0.22621.5624 (11 22h2), 10.0.22631.5624 (11

  1. Identify the current Windows version and build number by running 'winver' or 'systeminfo'
  2. Determine which affected version category your system falls under (Windows 10 1809, 10 21h2, 10 22h2, Windows 11 22h2, 23h2, or 24h2, Windows Server 2019, or Windows Server 2022)
  3. Apply the appropriate Windows Security Update that includes the fix for CVE-2025-49724
  4. For Windows 10 1809 / Server 2019: Update to build 10.0.17763.7558 or later
  5. For Windows 10 21h2: Update to build 10.0.19044.6093 or later
  6. For Windows 10 22h2: Update to build 10.0.19045.6093 or later
  7. For Windows 11 22h2: Update to build 10.0.22621.5624 or later
  8. For Windows 11 23h2: Update to build 10.0.22631.5624 or later
Caveat Standard Windows monthly cumulative updates typically have minimal breaking changes; ensure backup of critical data before applying

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
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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