Security readout for executives and security teams
Plain-English summary
A user who already has local, low-level access to an affected Windows system could exploit a kernel memory race condition to gain higher privileges. Successful exploitation could enable complete control over system data and operations. This is not described as remotely exploitable, but it materially increases the impact of stolen credentials, malware, or an existing foothold.
Executive priority
Treat as a high-priority patching item, especially on sensitive servers and systems exposed to multiple users. It requires an existing local foothold, reducing immediate risk compared with remote compromise, but successful exploitation could provide full privileged control. Track remediation to completion using Microsoft’s exact release-specific guidance.
Technical view
CVE-2026-20809 is a local Windows Kernel Memory elevation-of-privilege vulnerability involving a time-of-check/time-of-use race condition. It is classified under CWE-367 and CWE-122. The CVSS 3.1 score is 7.8, with low attack complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.
Likely exposure
Exposure includes the listed Windows 10, Windows 11, and Windows Server releases, including Server Core variants. Prioritize shared servers, administrator workstations, virtual desktop hosts, and endpoints where untrusted or compromised users can execute locally. The supplied version entries identify product baselines but do not provide exact patched build or KB numbers.
Exploitation context
The attacker must already be authorized and able to act locally with low privileges. The supplied sources do not establish active exploitation, public exploit availability, or remote attackability. The bundle marks KEV as false; this does not prove exploitation is absent. Exploit maturity is recorded as unproven in the CVSS vector.
Researcher notes
Public technical detail in the supplied bundle is limited to TOCTOU, kernel memory, and the CWE classifications. It does not describe the affected kernel component, race window, memory-corruption mechanics, indicators, or exploit reliability. Avoid inferring those details. Validate exposure through Microsoft’s product-specific security-update information rather than relying only on the baseline version strings.
Mitigation direction
- Apply the applicable Microsoft security update identified through the MSRC advisory and supported update-management channels.
- Prioritize affected systems permitting local execution by untrusted, shared, or previously compromised accounts.
- Restrict unnecessary local logon and code-execution access until affected systems are updated.
- Review Microsoft guidance for exact KB numbers, supported builds, prerequisites, and restart requirements.
Validation and detection
- Inventory listed Windows client and server releases, including Server Core installations.
- Compare installed build and update history against the current Microsoft advisory for each operating-system release.
- Confirm deployment success and required restarts through endpoint or patch-management reporting.
- Investigate unexpected privilege changes or privileged process activity; the sources provide no vulnerability-specific indicators.
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-122: 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-367: 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-20809 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:L/PR:L/UI:N/S:U/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:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C1.85.9microsoftVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: 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
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 Kernel Memory 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.
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Time-of-check Time-of-use (TOCTOU) Race Condition
Time-of-check Time-of-use (TOCTOU) Race Condition represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.