Code execution via heap-based buffer overflow
Published Mar 10, 2026 · Updated Mar 10, 2026
Heap-based buffer overflow in Microsoft Office Excel allows attackers to execute code locally after required user interaction. Microsoft identifies Excel heap-memory handling as the affected locus but has not disclosed the input field or incorrect bounds operation that triggers the overwrite. Exploitation requires a user action and executes code in that user's context; no network service exposure is reported.
Summary
What happened
Heap-based buffer overflow in Microsoft Office Excel allows attackers to execute code locally after required user interaction. Microsoft identifies Excel heap-memory handling as the affected locus but has not disclosed the input field or incorrect bounds operation that triggers the overwrite. Exploitation requires a user action and executes code in that user's context; no network service exposure is reported.
The record
- CVE
- CVE-2026-26108
- Published
- Mar 10, 2026
- Updated
- Mar 10, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2024
- Classifications
- CWE-122, CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 10, 2026CVE publishedPublication date reported by the CVE source.
- Mar 10, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=16.0.0 <16.107.26030819
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo