CVE-2026-24295
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 · uneditedConcurrent execution using shared resource with improper synchronization ('race condition') in Windows Device Association 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 confidenceA race condition exists in the Windows Device Association Service where concurrent execution with improper synchronization allows an authenticated local attacker to elevate privileges to SYSTEM level by exploiting timing windows in the service's handling of device association operations.
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< 10.0.14393.8957< 10.0.17763.8511< 10.0.19044.7058< 10.0.19045.7058< 10.0.22631.6783< 10.0.26100.7979< 10.0.26200.7979< 10.0.28000.1719CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify the Device Association Service is runningOpen Services.msc, locate 'Device Association Service', and check its Status column; or run 'sc query DeviceAssociationService' in an elevated command promptAffected if The service Status shows 'RUNNING' - this is required for the race condition to be exploitable
-
Confirm Windows build version is within affected rangeRun 'winver' or 'systeminfo | findstr /B /C:"OS Version"' to obtain the full build number (e.g., 10.0.19045.7058)Affected if The build number is lower than any of these thresholds: 14393.8957 (Win10 1607), 17763.8511 (Win10 1809), 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)
-
Identify if the service host process is activeOpen Task Manager, go to the Details tab, and look for 'dasHost.exe'; or run 'tasklist | findstr dasHost' in command promptAffected if The dasHost.exe process is present and running under a privileged account context (typically SYSTEM or LocalService)
-
Verify local authentication access existsConfirm the presence of local user accounts or domainjoined accounts on the system; this is a local privilege escalation requiring an authenticated user contextAffected if An authenticated local user account (even low-privilege) exists on the machine, as the attacker needs this to initiate the race condition exploitation
The system is affected if the Device Association Service is running AND the Windows build version falls below the fixed version thresholds for the corresponding Windows release, allowing a local authenticated user to attempt the race condition privilege escalation.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.14393.895710.0.17763.851110.0.19044.7058
Apply the relevant Microsoft security update for CVE-2026-24295 when released; if the Device Association Service is not required in the environment, consider disabling it to reduce attack surface.
Install the security update corresponding to your Windows version from Microsoft Update. The fixed build versions are: Windows 10 1607 (10.0.14393.8957), Windows 10 1809 (10.0.17763.8511), Windows 10 21h2 (10.0.19044.7058), Windows 10 22h2 (10.0.19045.7058), Windows 11 23h2 (10.0.22631.6783), Window
- 1. Open Windows Settings and navigate to Update & Security > Windows Update
- 2. Click 'Check for updates' to ensure you have the latest security patches
- 3. If automatic updates are disabled, manually download and install the relevant security update from the Microsoft Catalog (catalog.update.microsoft.com)
- 4. Search for the specific KB article associated with this CVE (check msrc.microsoft.com for the corresponding KB number)
- 5. After installation, restart the system to complete the patch application
- 6. Verify the update was installed by checking the installed updates list in Control Panel > Programs and Features > View installed updates
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24295 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24295 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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