Security readout for executives and security teams
Plain-English summary
This Windows flaw could let a user or attacker with limited local access gain much greater control of an affected computer. It is not remotely exploitable by itself, but it could turn an initial foothold into a serious system compromise affecting sensitive data, system integrity, and availability.
Executive priority
Use an accelerated, risk-based patch cycle. This is not a standalone remote-entry vulnerability, but it can materially amplify an existing compromise. Prioritize sensitive servers, administrator endpoints, shared systems, and environments where lower-privileged users or workloads can run local code.
Technical view
CVE-2026-35416 is a local privilege-escalation vulnerability in the Windows Ancillary Function Driver for WinSock. The supplied description identifies type confusion, while the supplied CWE is CWE-416, use-after-free; that inconsistency remains unresolved. Exploitation requires low privileges, no user interaction, and high attack complexity. CVSS 3.1 is 7.0.
Likely exposure
Exposure spans the listed Windows 10, Windows 11, and Windows Server releases, including several Server Core installations. Systems are most likely exposed when running an affected release without its applicable Microsoft security update. The bundle does not identify specific KB numbers or fixed build versions.
Exploitation context
The vulnerability requires local access and existing low-level privileges, so it is primarily useful after an attacker has already gained a foothold. High attack complexity reduces reliability, but successful exploitation could substantially increase control. The bundle marks it as absent from KEV and provides no evidence of active exploitation or public exploit availability.
Researcher notes
The available evidence establishes local attack vector, low required privileges, high complexity, no user interaction, unchanged scope, and high confidentiality, integrity, and availability impact. It does not provide root-cause detail, exploit primitives, fixed builds, KB identifiers, or telemetry indicators. Reconcile the type-confusion description with the CWE-416 classification before relying on weakness-specific detections.
Mitigation direction
- Review Microsoft's advisory for applicable security updates and installation requirements.
- Prioritize affected internet-facing servers, privileged workstations, and systems where untrusted users can execute code.
- Apply the applicable Microsoft security update through established patch-management processes.
- Restrict local access and software execution where patching cannot be completed promptly.
- Check Microsoft guidance for any subsequently published workarounds or mitigations.
Validation and detection
- Inventory endpoints and servers running the affected Windows releases listed in the advisory.
- Map each affected system to Microsoft's applicable security update and fixed build information.
- Verify update installation and required restart completion through endpoint-management records.
- Confirm deployed operating-system builds no longer fall within Microsoft's affected criteria.
- Monitor for unexpected privilege elevation on affected systems while remediation remains incomplete.
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-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-35416 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 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:H/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:H/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C15.9microsoftVulnerability scoring details
Base CVSS 3.1 score
7HighVector: CVSS:3.1/AV:L/AC:H/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.
Use After Free
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.