LiveActive security incident?Get immediate response
CVE Record

CVE-2026-20839: Windows Client-Side Caching (CSC) Service Information Disclosure Vulnerability

Improper access control in Windows Client-Side Caching (CSC) Service allows an authorized attacker to disclose information locally.

MediumCVSS 5.5Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A user who already has authorized local access to an affected Windows computer may obtain information they should not be permitted to see through the Client-Side Caching service. The issue threatens confidentiality but is not reported to alter data or disrupt systems.

Executive priority

Schedule remediation through the normal security-update cycle, accelerating shared or sensitive systems. The moderate rating reflects substantial possible confidentiality loss but required authorized local access and no reported active exploitation. Escalate if Microsoft later reports exploitation or affected systems contain particularly sensitive cached information.

Technical view

CVE-2026-20839 is an improper access control flaw (CWE-284) in Windows Client-Side Caching. Exploitation requires local access and low privileges, with low complexity and no user interaction. Its CVSS 3.1 score is 5.5; the assessed impact is high confidentiality loss without integrity or availability impact.

Likely exposure

Exposure spans listed Windows 10, Windows 11, and Windows Server releases, including several Server Core installations. Prioritize shared workstations, multi-user servers, and systems handling sensitive cached files. The bundle provides baseline version identifiers, not complete affected build ranges, so confirm applicability through Microsoft guidance.

Exploitation context

The supplied record does not establish active exploitation. It is not identified as a CISA KEV, and the CVSS vector marks exploit maturity as unproven. Because an attacker needs authorized local access, this is primarily a post-access confidentiality risk rather than a remote initial-compromise path.

Researcher notes

The record indicates local, low-privilege exploitation with no user interaction and high confidentiality impact. It does not describe the exposed information, affected build boundaries, prerequisites involving Offline Files, or technical root cause beyond improper access control. Avoid inferring those details; use the Microsoft advisory for product-specific applicability and update information.

Mitigation direction

  • Review the Microsoft advisory for the security update applicable to each Windows release.
  • Deploy applicable Microsoft security updates through the normal tested patch process.
  • Prioritize systems storing sensitive data or accessible by multiple local users.
  • Restrict unnecessary local accounts and privileges while remediation is pending.

Validation and detection

  • Inventory endpoints and servers running the listed Windows releases.
  • Compare installed builds and update status with current Microsoft applicability guidance.
  • Confirm applicable security updates installed successfully and systems completed any required restart.
  • Review local account access on sensitive or shared affected systems.
  • Document exceptions where Microsoft applicability or update evidence remains unclear.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-284: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-20839 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.5CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C1.83.6microsoft

Vulnerability scoring details

Base CVSS 3.1 score

5.5Medium
CVSS 3.1 vector shape for CVE-2026-20839Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MicrosoftWindows 10 Version 160710.0.14393.0Listed
MicrosoftWindows 10 Version 180910.0.17763.0Listed
MicrosoftWindows 10 Version 21H210.0.19044.0Listed
MicrosoftWindows 10 Version 22H210.0.19045.0Listed
MicrosoftWindows 11 version 23H210.0.22631.0Listed
MicrosoftWindows 11 Version 23H210.0.22631.0Listed
MicrosoftWindows 11 Version 24H210.0.26100.0Listed
MicrosoftWindows 11 Version 25H210.0.26200.0Listed
MicrosoftWindows Server 2008 R2 Service Pack 16.1.7601.0Listed
MicrosoftWindows Server 2008 R2 Service Pack 1 (Server Core installation)6.1.7601.0Listed
MicrosoftWindows Server 20126.2.9200.0Listed
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0Listed
MicrosoftWindows Server 2012 R26.3.9600.0Listed
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0Listed
MicrosoftWindows Server 201610.0.14393.0Listed
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0Listed
MicrosoftWindows Server 201910.0.17763.0Listed
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0Listed
MicrosoftWindows Server 202210.0.20348.0Listed
MicrosoftWindows Server 2022, 23H2 Edition (Server Core installation)10.0.25398.0Listed
MicrosoftWindows Server 202510.0.26100.0Listed
MicrosoftWindows Server 2025 (Server Core installation)10.0.26100.0Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-284 · source CWE mapping

Improper Access Control

Improper Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.