dbcve.org
Windows 10 1809Operating system · Microsoft

CVE-2026-24292

HIGH · 7.8 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.17763.8511 / 10.0.19044.7058 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 Connected Devices Platform Service (Cdpsvc) 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

Use after free vulnerability in Windows Connected Devices Platform Service (Cdpsvc) allows a locally authenticated attacker to elevate privileges to SYSTEM level via memory corruption.

MitigationDeploy Microsoft security update addressing CVE-2026-24292; if Cdpsvc is not required, consider disabling the service after verifying no dependent features are in use.

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.8511
Windows 10 21h2Operating system
Affected:< 10.0.19044.7058
Windows 10 22h2Operating system
Affected:< 10.0.19045.7058
Windows 11 23h2Operating system
Affected:< 10.0.22631.6783
Windows 11 24h2Operating system
Affected:< 10.0.26100.7979
Windows 11 25h2Operating system
Affected:< 10.0.26200.7979
Windows 11 26h1Operating system
Affected:< 10.0.28000.1719
Windows Server 2019Operating system
Affected:< 10.0.17763.8511

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. Verify Cdpsvc service is present
    Run `Get-Service -Name Cdpsvc` in PowerShell or check Services list for 'Connected Devices Platform Service'
    Affected if Service exists and is set to Manual or Running status - the vulnerability only applies when this service is enabled
  2. Check Windows version number
    Run `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"` to obtain the exact build version
    Affected if Build number falls below the fixed version for your Windows release: 17763.8511 (Win10 1809/Server2019), 19044.7058 (Win10 21h2), 19045.7058 (Win10 22h2), 22631.6783 (Win11 23h2), 26100.7979 (Win11 24h2), 26200.7979 (Win11 25h2), or 28000.1719 (Win11 26h1)
  3. Confirm security update installation
    Run `Get-HotFix | Where-Object {$_.Description -match "Security Update"} | Sort-Object InstalledOn -Descending | Select-Object -First 10` to list recent security patches, or check Windows Update history for the CVE-2026-24292 update
    Affected if No security update addressing CVE-2026-24292 appears in installed updates and version remains below fixed build

If Cdpsvc service is enabled and the Windows build version is below the fixed threshold with no corresponding security update installed, the environment is vulnerable.

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.8511 / 10.0.19044.7058 / 10.0.19045.7058 or later
Fixed in 10.0.17763.851110.0.19044.705810.0.19045.7058
Interim mitigation

Deploy Microsoft security update addressing CVE-2026-24292; if Cdpsvc is not required, consider disabling the service after verifying no dependent features are in use.

Recommended fix High confidence

Windows 10 1809/Server 2019: 10.0.17763.8511 or later | Windows 10 21h2: 10.0.19044.7058 or later | Windows 10 22h2: 10.0.19045.7058 or later | Windows 11 23h2: 10.0.22631.6783 or later | Windows 11 24h2: 10.0.26100.7979 or later | Windows 11 25h2: 10.0.26200.7979 or later | Windows 11 26h1: 10.0.28

  1. Open Settings > Update & Security > Windows Update and check for updates
  2. Install all available Windows security updates, which will include the fix for this vulnerability
  3. Restart the system when prompted to complete the installation
  4. Verify the update was installed by running 'winver' and confirming the build number meets or exceeds the fixed version for your Windows release
Caveat Standard Windows security update; may require system restart. No expected breaking changes for this privilege escalation patch.

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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