Security readout for executives and security teams
Plain-English summary
This flaw can let a user who already has local access gain higher Windows privileges. Successful exploitation could expose sensitive data, alter systems, or disrupt services. It is serious but requires local access and a difficult race condition.
Executive priority
Treat this as a high-priority patching issue, especially on shared servers and privileged workstations. It is not presented as an emergency internet-wide threat because exploitation is local, complex, and unsupported by active-exploitation evidence. Track remediation through normal high-severity timelines and escalate exposed multi-user systems.
Technical view
Windows Management Services contains improper synchronization involving a shared resource, categorized as a race condition and use-after-free. A low-privileged local attacker can attempt privilege escalation without user interaction. CVSS 3.1 rates it 7.8, with high complexity, changed scope, and high confidentiality, integrity, and availability impacts.
Likely exposure
Exposure applies to the listed Windows 10, Windows 11, and Windows Server editions where Microsoft's correction has not been applied. The attack vector is local, so internet exposure alone does not establish vulnerability. Systems allowing untrusted or compromised users local execution deserve greater priority.
Exploitation context
The bundle provides no evidence of active exploitation, and the CVE is not listed in KEV. The CVSS exploit-maturity value is unproven. Exploitation requires existing low-level local authorization and winning a high-complexity race condition; no user interaction is required.
Researcher notes
The public bundle identifies CWE-362 and CWE-416 but does not provide detailed affected code paths, patch KB numbers, indicators, or proof-of-concept information. The affected-version entries appear to identify Windows release baselines rather than explicit vulnerable build ranges; validate applicability and corrected builds against Microsoft's advisory.
Mitigation direction
- Review Microsoft's CVE advisory and identify the applicable security update for each affected Windows edition.
- Deploy Microsoft's applicable security updates through the organization's normal Windows patching process.
- Prioritize multi-user servers, administrative workstations, and systems where untrusted users can execute locally.
- Restrict unnecessary local access while patching is pending.
Validation and detection
- Inventory listed Windows editions and compare their patch status with Microsoft's CVE advisory.
- Confirm the applicable Microsoft security update is installed on each in-scope endpoint and server.
- Re-scan patched systems using current vulnerability-management content.
- Review exceptions and unsupported systems, documenting compensating access restrictions and remediation ownership.
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-20874 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.