Security readout for executives and security teams
Plain-English summary
This Windows flaw lets a user who already has local, low-level access gain much greater control of an affected computer. Successful exploitation could expose data, alter systems, or disrupt services. It is serious because exploitation requires no user interaction and has low stated complexity.
Executive priority
Prioritize remediation in the normal high-severity patch cycle, accelerating critical servers and privileged-user endpoints. This vulnerability is not evidenced as actively exploited, but it can convert limited local access into full system compromise with potentially severe business impact.
Technical view
CVE-2026-20860 is a local type-confusion vulnerability (CWE-843) in the Windows Ancillary Function Driver for WinSock. An authorized, low-privileged attacker can elevate privileges. Its CVSS 3.1 score is 7.8, with high confidentiality, integrity, and availability impacts; scope remains unchanged.
Likely exposure
Exposure applies to the listed Windows 10, Windows 11, and Windows Server releases, including several Server Core installations. Exploitation requires local access and existing low privileges, so internet exposure alone is not sufficient. Shared workstations, multi-user servers, and systems where an attacker could first obtain credentials deserve particular attention.
Exploitation context
The supplied record does not identify this CVE as CISA KEV and provides no evidence of active exploitation. The CVSS exploit-maturity value is unproven. Treat it as a significant privilege-escalation opportunity that could follow initial access, not as a remotely exploitable entry point.
Researcher notes
The supplied sources establish local attack vector, low complexity, low required privileges, no user interaction, and type confusion in the WinSock ancillary driver. They do not provide root-cause detail, affected code paths, exploit samples, fixed build numbers, or telemetry guidance. Confirm release-specific remediation directly in Microsoft’s advisory.
Mitigation direction
- Apply the Microsoft security update appropriate to each affected Windows release.
- Consult Microsoft’s advisory for exact update packages and release-specific requirements.
- Prioritize shared systems, administrative workstations, and servers where local compromise would have substantial impact.
- Restrict unnecessary local accounts and privileges while updates are being deployed.
Validation and detection
- Inventory systems running the Windows releases and versions identified in the affected-product list.
- Compare installed update status against Microsoft’s CVE advisory for each operating-system release.
- Use authenticated vulnerability scanning or endpoint-management reporting to confirm remediation coverage.
- Investigate unpatched systems and document exceptions, ownership, and remediation deadlines.
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-843: 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-20860 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 Ancillary Function Driver for WinSock 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.
Access of Resource Using Incompatible Type ('Type Confusion')
Access of Resource Using Incompatible Type ('Type Confusion') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.