Security readout for executives and security teams
Plain-English summary
This Windows flaw can let an already authorized local user gain higher privileges by triggering a timing error in Windows Management Services. Successful exploitation could compromise confidentiality, integrity, and availability. It is serious for shared workstations, servers, and systems where lower-privileged users or processes may run.
Executive priority
Treat as a high-priority patching item, especially on multi-user endpoints and important servers. It is not described as remotely exploitable or actively exploited, reducing immediate emergency pressure. Establish affected-system counts, prioritize higher-consequence assets, and track Microsoft update deployment to completion.
Technical view
CVE-2026-20873 is a local elevation-of-privilege vulnerability involving improper synchronization of a shared resource. It is classified under CWE-362 and CWE-416. Exploitation requires low privileges, no user interaction, and high attack complexity. The CVSS 3.1 score is 7.8, with potentially high confidentiality, integrity, and availability impact.
Likely exposure
Exposure includes the listed Windows 10, Windows 11, and Windows Server releases, including specified Server Core installations. An attacker must already have authorized local access. Confirm actual exposure through operating-system inventory and Microsoft update status; the bundle does not identify vulnerable application configurations or compensating controls.
Exploitation context
The source bundle provides no evidence of active exploitation, and the CVE is not identified as KEV. The CVSS vector reports unproven exploit maturity and high attack complexity. Risk remains meaningful because successful exploitation could convert limited local access into elevated privileges.
Researcher notes
The affected data lists base version identifiers but no CPEs or specific fixed builds. Windows 11 23H2 appears twice with capitalization differences. Researchers should rely on Microsoft’s advisory for authoritative applicability and update mapping. The available evidence supports a synchronization race with a use-after-free classification, but does not disclose the vulnerable component path or exploitation mechanics.
Mitigation direction
- Review Microsoft’s CVE advisory for the applicable security update and deployment requirements.
- Apply the Microsoft-provided update to affected, supported Windows systems using normal change controls.
- Prioritize shared systems, servers, and endpoints permitting lower-privileged local users or processes.
- Restrict unnecessary local access while remediation is pending.
- Check Microsoft guidance for any product-specific mitigations or prerequisites.
Validation and detection
- Inventory Windows editions, versions, build numbers, and Server Core installations against the affected list.
- Verify each affected system has the update specified by Microsoft’s CVE advisory.
- Confirm update deployment succeeded and systems report expected post-update status.
- Re-scan managed endpoints after deployment and investigate remaining vulnerable results.
- Review privileged-account changes or unexpected elevation activity on exposed systems.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-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 lookupCWE-416: 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 lookupPrivilege behavior lookup
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-20873 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C
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.
SSVC decision data
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C1.16microsoftVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Windows Management Services Elevation of Privilege VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
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.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.