dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2026-20815

HIGH · 7.0 CVSS v3.1 Published 2026-01-13
Fix available
A fix is available. Upgrade to 10.0.26100.7623 / 10.0.26100.32230 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
Concurrent execution using shared resource with improper synchronization ('race condition') in Capability Access Management Service (camsvc) allows an authorized attacker to elevate privileges locally.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 7mo ago

Surfaced from public web coverage — external links open in a new tab.

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 race condition exists in the Capability Access Management Service (camsvc) where concurrent access to shared resources lacks proper synchronization. An authorized local attacker can exploit this timing vulnerability to manipulate the service's behavior and elevate their privileges to a higher permission level.

MitigationApply vendor-supplied patches for camsvc when available; until then, limit local access to trusted users only and monitor for suspicious process activity targeting the capability access management service.

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 11 24h2Operating system
Affected:< 10.0.26100.7623
Windows 11 25h2Operating system
Affected:< 10.0.26200.7623
Windows Server 2025Operating system
Affected:< 10.0.26100.32230

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. Identify the Windows version and build number
    Run 'winver' or 'systeminfo' in Command Prompt, or use 'Get-ComputerInfo | Select-Object WindowsProductName,OsVersion,OsBuildNumber' in PowerShell
    Affected if The system is Windows 11 24h2, Windows 11 25h2, or Windows Server 2025 with a build number below the fixed versions (26100.7623 for 24h2, 26200.7623 for 25h2, 26100.32230 for Server 2025)
  2. Verify the Capability Access Management Service (camsvc) is present
    Run 'Get-Service camsvc' in PowerShell or check Services list for 'Capability Access Management Service'
    Affected if The camsvc service exists on the system, indicating it is a vulnerable Windows version where this service is included
  3. Confirm camsvc is running
    Run 'Get-Service camsvc | Select-Object Status' in PowerShell or check the service status in Services.msc
    Affected if The camsvc service status is 'Running', meaning the exploitable code path is active
  4. Check OS build against vulnerable version thresholds
    Compare the OS build number from step 1 against: Windows 11 24h2 < 10.0.26100.7623, Windows 11 25h2 < 10.0.26200.7623, Windows Server 2025 < 10.0.26100.32230
    Affected if The installed build number falls below the corresponding fixed build for the detected Windows edition

The system is affected if it runs Windows 11 24h2, 25h2, or Windows Server 2025 with a build number lower than the fixed thresholds and the camsvc service is present and running.

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.26100.7623 / 10.0.26100.32230 / 10.0.26200.7623 or later
Fixed in 10.0.26100.762310.0.26100.3223010.0.26200.7623
Interim mitigation

Apply vendor-supplied patches for camsvc when available; until then, limit local access to trusted users only and monitor for suspicious process activity targeting the capability access management service.

Recommended fix High confidence

Windows 11 24h2: build 10.0.26100.7623 or later | Windows 11 25h2: build 10.0.26200.7623 or later | Windows Server 2025: build 10.0.26100.32230 or later

  1. Check current Windows version by running `winver` or `systeminfo | findstr /B /C:"OS Name" /C:"OS Version"`
  2. Open Settings > Windows Update > Check for updates
  3. Install all available security updates, specifically looking for the KB patch addressing CVE-2026-20815
  4. Alternatively, manually download the update from the Microsoft Update Catalog website for your specific Windows version
  5. Restart the system after installing the update
  6. Verify the update was applied by checking the installed KB articles or re-running `winver` to confirm the build number meets or exceeds: 10.0.26100.7623 (Windows 11 24h2), 10.0.26200.7623 (Windows 11 25h2), or 10.0.26100.32230 (Windows Server 2025)
Caveat Standard Windows security updates typically have no breaking changes; however, ensure backups are made and critical applications are tested after any system update

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

Fix this in Windows 11 24h2 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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