Security readout for executives and security teams
Plain-English summary
A local user who already has authorized access to a vulnerable Windows device could exploit a memory-handling flaw in Microsoft Office Click-to-Run to gain higher privileges. Successful exploitation could compromise sensitive data, alter the system, or disrupt service. It is high severity, but the supplied evidence does not show remote exploitation or active attacks.
Executive priority
Treat this as a high-priority endpoint patching issue. It is not documented here as remotely exploitable or actively exploited, but it can turn limited local access into broad system compromise. Direct vulnerability management teams to establish affected build counts, deploy Microsoft's update, and escalate exceptions on sensitive or multi-user systems.
Technical view
CVE-2026-35436 is a use-after-free vulnerability in Microsoft Office Click-to-Run. It requires local access and low privileges, needs no user interaction, and can cross a security boundary. Microsoft assigns CVSS 3.1 score 8.8, with potentially high confidentiality, integrity, and availability impact. Exact vulnerable builds and exploitation mechanics are not established by the supplied bundle.
Likely exposure
Potentially exposed environments include those running Microsoft 365 Apps for Enterprise, Office 2019, Office LTSC 2021, or Office LTSC 2024. The listed version identifiers are broad and insufficient for reliable build-level conclusions. Inventory installed Office products, update channels, architectures, and build numbers, then compare them with Microsoft's advisory.
Exploitation context
Exploitation requires an authorized attacker with local, low-privileged access; no user interaction is indicated. The CVSS exploit-maturity value is unproven, and the CVE is not listed as CISA KEV in the supplied bundle. Therefore, active exploitation is not established. The flaw could nevertheless amplify damage after initial account or endpoint compromise.
Researcher notes
The supplied record identifies a use-after-free and CWE-1220, but provides no detailed vulnerable object, component path, attack sequence, update identifiers, or fixed-build matrix. Avoid inferring affected builds from the broad version strings alone. Validate scope and remediation directly against the Microsoft advisory. No supplied evidence supports public proof-of-concept availability or observed exploitation.
Mitigation direction
- Review Microsoft's CVE advisory for affected builds and the applicable security update.
- Prioritize updating exposed shared workstations, virtual desktops, and systems handling sensitive information.
- Confirm Office Click-to-Run update policies are functioning across every deployment channel.
- Restrict unnecessary local access and promptly investigate compromised or unexpected user accounts.
- Use vendor guidance for any systems that cannot be updated immediately.
Validation and detection
- Inventory Office product, architecture, update channel, and exact build on managed endpoints.
- Compare collected builds with Microsoft's current affected and remediated version tables.
- Verify the applicable security update installed successfully and survived a restart.
- Rescan endpoints and investigate devices that remain outdated or report update failures.
- Monitor endpoint telemetry for unexpected privilege changes originating from Office-related processes.
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-1220: 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-35436 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
- 8.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/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:L/PR:L/UI:N/S:C/C:H/I:H/A:H/E:U/RL:O/RC:C26microsoftVulnerability scoring details
Base CVSS 3.1 score
8.8HighVector: CVSS:3.1/AV:L/AC:L/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
- Microsoft Office Click-To-Run 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.
Insufficient Granularity of Access Control
Insufficient Granularity of Access Control represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.