Security readout for executives and security teams
Plain-English summary
This is a high-severity Microsoft Office code execution issue caused by type confusion. If exposed, affected Office installations could allow an unauthorized attacker to run code locally with serious confidentiality, integrity, and availability impact.
Executive priority
Treat as a high-priority patching item for Office fleets. No active exploitation is evidenced in the supplied sources, but the potential impact is full compromise of confidentiality, integrity, and availability on affected endpoints.
Technical view
CVE-2026-26110 is CWE-843 type confusion in Microsoft Office. The supplied CVSS 3.1 score is 8.4 with local attack vector, low complexity, no privileges, no user interaction, unchanged scope, and high C/I/A impact.
Likely exposure
Exposure is likely where listed Microsoft Office, Microsoft 365 Apps for Enterprise, Office LTSC, Mac LTSC, or Office for Android versions are deployed and not updated per Microsoft guidance.
Exploitation context
The provided bundle does not show CISA KEV listing or active exploitation. Exploit maturity is marked unproven, so urgency is driven by impact and Microsoft patch availability, not confirmed in-the-wild use.
Researcher notes
Sources identify type confusion but do not provide affected component details, trigger conditions, proof-of-concept status, or fixed build numbers in the bundle. Avoid assuming document-based delivery unless Microsoft publishes that detail.
Mitigation direction
- Apply Microsoft updates referenced by the MSRC advisory.
- Prioritize systems processing untrusted Office content or mobile Office files.
- Inventory affected Office, Microsoft 365 Apps, LTSC, Mac, and Android deployments.
- Monitor Microsoft guidance for fixed builds and deployment caveats.
- Use standard endpoint controls to reduce local code execution impact.
Validation and detection
- Confirm installed Office products match the affected product list.
- Verify update compliance against Microsoft’s CVE-2026-26110 advisory.
- Check vulnerability scanner coverage for CVE-2026-26110.
- Review asset inventories for Office LTSC, Mac LTSC, and Android Office exposure.
- Track whether the CVE later appears in CISA KEV or vendor threat updates.
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-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 lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2026-26110 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.4 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/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:N/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C2.55.9microsoftVulnerability scoring details
Base CVSS 3.1 score
8.4HighVector: CVSS:3.1/AV:L/AC:L/PR:N/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
- Microsoft Office Remote Code Execution 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.