LiveActive security incident?Get immediate response
CVE Record

CVE-2026-20826: Tablet Windows User Interface (TWINUI) Subsystem Information Disclosure Vulnerability

Concurrent execution using shared resource with improper synchronization ('race condition') in Tablet Windows User Interface (TWINUI) Subsystem allows an authorized attacker to elevate privileges locally.

HighCVSS 7.8Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

A logged-in attacker with limited privileges could exploit a race condition in Windows TWINUI to gain higher local privileges. Successful exploitation could compromise sensitive data, system integrity, and availability. The supplied title calls this information disclosure, but the description and CVSS impact indicate local privilege escalation; Microsoft’s advisory should govern classification and remediation.

Executive priority

Treat this as a high-priority patching issue, particularly where an initial low-privilege compromise could reach sensitive systems. It is not described as remotely exploitable or actively exploited in the supplied evidence, so prioritize by local-access likelihood and asset criticality rather than assuming an immediate internet-scale emergency.

Technical view

CVE-2026-20826 is a CWE-362 improper-synchronization flaw in the Windows TWINUI subsystem. It has CVSS 3.1 score 7.8: local access, low complexity, low privileges, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impacts. The bundle identifies multiple supported Windows client and server families as affected.

Likely exposure

Exposure exists on the listed Windows 10, Windows 11, and Windows Server releases when the applicable Microsoft security update is absent. Exploitation requires authorized local access, so internet exposure alone is insufficient. Shared endpoints, servers with interactive users, and systems where attackers may obtain an initial low-privilege foothold deserve particular attention.

Exploitation context

The supplied sources do not establish active exploitation, and the CVE is not identified as being in CISA’s Known Exploited Vulnerabilities catalog. Exploitation is local, requires low privileges, needs no user interaction, and is rated low complexity. It could therefore strengthen a broader attack after initial account or endpoint compromise.

Researcher notes

The source bundle contains a classification inconsistency: the title says information disclosure, while the description says elevation of privilege and the vector assigns high impact across confidentiality, integrity, and availability. The evidence supports a local race condition, but provides no technical root-cause detail, exploit prerequisites beyond the vector, indicators of compromise, or affected build ranges beyond listed versions.

Mitigation direction

  • Review Microsoft’s CVE advisory for updates applicable to each Windows release.
  • Deploy the applicable Microsoft security updates through normal patch-management controls.
  • Prioritize shared endpoints and servers where low-privilege users can sign in.
  • Restrict unnecessary local and interactive access while patch deployment remains incomplete.

Validation and detection

  • Inventory systems running the Windows client and server releases listed in the advisory.
  • Verify the applicable Microsoft security update is installed on each in-scope system.
  • Use authenticated vulnerability scanning or endpoint-management reporting to identify missing updates.
  • Retest representative systems after deployment and investigate failed or pending installations.
Prepared
Confidence
high
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 · low confidence lookup

CWE-362: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-20826 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
High
CVSS
7.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/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: total

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
7.8CVSS 3.1HighCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C1.85.9microsoft

Vulnerability scoring details

Base CVSS 3.1 score

7.8High
CVSS 3.1 vector shape for CVE-2026-20826Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/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 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-362 · source CWE mapping

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.