dbcve.org
Windows 11 24h2Operating system · Microsoft

CVE-2026-20835

MEDIUM · 5.5 CVSS v3.1 Published 2026-01-13
Fix available
A fix is available. Upgrade to 10.0.25398.2092 / 10.0.26100.7623 or later.
See remediation →
57/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
Out-of-bounds read in Capability Access Management Service (camsvc) allows an authorized attacker to disclose information 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

An out-of-bounds read vulnerability exists in Windows Capability Access Management Service (camsvc) that allows a locally authenticated attacker with authorized access to read memory outside intended boundaries, potentially exposing sensitive information.

MitigationApply vendor security updates for camsvc when available; limit local user privileges and monitor for unusual service behavior as interim controls.

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 2022 23h2Operating system
Affected:< 10.0.25398.2092
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
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

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 camsvc service presence
    Run 'Get-Service camsvc' or 'sc query camsvc' in PowerShell/command prompt to confirm the Capability Access Management Service exists on the system
    Affected if The service exists and is running - the vulnerability applies to this service when the Windows version is in the affected range
  2. Determine Windows edition and build version
    Run 'winver' or check 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the exact Windows version and build number
    Affected if The system is Windows 11 24h2 (build < 26100.7623), Windows 11 25h2 (build < 26200.7623), Windows Server 2022 23h2 (build < 25398.2092), or Windows Server 2025 (build < 26100.32230)
  3. Check camsvc binary version
    Locate the camsvc binary (commonly in C:\Windows\System32\) and run '(Get-Item "C:\Windows\System32\camsvc.dll").VersionInfo' or right-click > Properties > Details to view file version
    Affected if The camsvc binary version is lower than the corresponding patched version for the detected Windows build
  4. Confirm user context
    Verify the local user account privileges using 'whoami /all' or checking Local Users and Groups (lusrmgr.msc) - the attacker needs local authenticated access
    Affected if The system has user accounts with local authentication capability (standard condition for most Windows installations)

The system is affected if camsvc service is present, the Windows build number is below the patched thresholds listed for each version, and the attacker has local authenticated access to the 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.25398.2092 / 10.0.26100.7623 / 10.0.26100.32230 or later
Fixed in 10.0.25398.209210.0.26100.762310.0.26100.32230
Interim mitigation

Apply vendor security updates for camsvc when available; limit local user privileges and monitor for unusual service behavior as interim controls.

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 2022 23h2: build 10.0.25398.2092 or later | Windows Server 2025: build 10.0.26100.32230 or later

  1. Identify current Windows version by running `winver` or checking System Information
  2. Determine the specific build number needed based on your Windows edition (24h2, 25h2, Server 2022 23h2, or Server 2025)
  3. Apply Windows security updates via Windows Update, or manually download and install the appropriate cumulative update for your version
  4. Restart the system after applying the update
  5. Verify the installed version meets or exceeds the minimum fixed build: Windows 11 24h2 requires 10.0.26100.7623, Windows 11 25h2 requires 10.0.26200.7623, Windows Server 2022 23h2 requires 10.0.25398.2092, Windows Server 2025 requires 10.0.26100.32230
Caveat Standard Windows update risks apply - ensure backups and compatibility testing for critical systems before deployment

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
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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