CVE-2026-26110
Type Confusion in Microsoft Office Enables Local Code Execution
Publication date: 2026-03-10
Last updated on: 2026-03-13
Assigner: Microsoft Corporation
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| microsoft | office | 2016 |
| microsoft | 365_apps | * |
| microsoft | 365_apps | * |
| microsoft | office | 2016 |
| microsoft | office_long_term_servicing_channel | 2021 |
| microsoft | office | 2019 |
| microsoft | office | 2019 |
| microsoft | office_long_term_servicing_channel | 2024 |
| microsoft | office_long_term_servicing_channel | 2021 |
| microsoft | office_long_term_servicing_channel | 2021 |
| microsoft | office_long_term_servicing_channel | 2024 |
| microsoft | office_long_term_servicing_channel | 2024 |
| microsoft | office | to 16.0.19822.20000 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-843 | The product allocates or initializes a resource such as a pointer, object, or variable using one type, but it later accesses that resource using a type that is incompatible with the original type. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a type confusion issue in Microsoft Office where an attacker can access a resource using an incompatible type. This flaw allows an unauthorized attacker to execute code locally on the affected system.
How can this vulnerability impact me? :
The vulnerability can lead to local code execution by an unauthorized attacker, which means the attacker could run malicious code on your system without permission. This can result in full compromise of confidentiality, integrity, and availability of your data and system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, it is recommended to apply the security updates provided by Microsoft for Microsoft Office as soon as they become available.
Since the vulnerability allows local code execution via type confusion, limiting user privileges and avoiding opening untrusted Office documents can reduce risk until patches are applied.