Security readout for executives and security teams
Plain-English summary
A user who already has authorized local access to an affected Windows system may exploit a memory-management flaw to gain higher privileges. Successful exploitation could compromise sensitive information, alter the system, or disrupt services. This is primarily a post-compromise escalation risk, not a remote initial-entry vulnerability.
Executive priority
Treat this as a high-priority Windows patching issue, particularly on shared endpoints and important servers. It requires an existing foothold, which reduces immediate exposure, but successful exploitation could turn limited access into broad system compromise. Remediate through the next accelerated patch cycle and track exceptions.
Technical view
CVE-2026-20858 is a local elevation-of-privilege vulnerability in Windows Management Services involving a race condition and use-after-free. CVSS 3.1 is 7.8: local access, low privileges, high attack complexity, no user interaction, changed scope, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure is limited to the listed Windows 10, Windows 11, and Windows Server releases. Risk is greatest where untrusted users have local access or another compromise provides low-privileged execution. The source bundle does not specify service prerequisites, vulnerable build ranges, or configuration-dependent exposure.
Exploitation context
An attacker must already be authorized locally with low privileges, and exploitation is rated high complexity. No user interaction is required. The supplied evidence does not establish public exploit availability or active exploitation, and the CVE is not identified as being in CISA's Known Exploited Vulnerabilities catalog.
Researcher notes
The weakness mapping combines CWE-362 race condition behavior with CWE-416 use-after-free. The changed-scope vector is notable, but the bundle provides no affected component details, trigger conditions, exploitability assessment beyond high complexity, or specific update identifiers. Researchers should rely on Microsoft for build-level applicability and avoid inferring undocumented prerequisites.
Mitigation direction
- Review Microsoft's CVE advisory and identify the applicable security update for each affected release.
- Prioritize updates on multi-user systems, administrative workstations, and servers exposed to low-privileged users.
- Apply applicable Microsoft security updates through the organization's standard tested patch process.
- Restrict unnecessary local access while systems remain unpatched.
- Monitor Microsoft guidance for revised affected-build or mitigation information.
Validation and detection
- Inventory systems running the Windows releases listed in the source bundle.
- Map installed builds and updates against Microsoft's current CVE advisory.
- Confirm applicable security updates installed successfully on each exposed asset.
- Re-scan patched assets and investigate systems still reporting vulnerability.
- Review local account and endpoint telemetry for unexpected privilege elevation activity.
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-20858 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:T/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:T/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:T/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.