Code execution via out-of-bounds memory write
Published Aug 11, 2026 · Updated Aug 25, 2026
Out-of-bounds write in Microsoft Office Excel allows attackers to execute code locally after required user interaction. The published record does not identify the input that reaches the faulty write or the affected Excel routine. Successful exploitation runs code in the user's context and can compromise confidentiality, integrity, and availability.
Summary
What happened
Out-of-bounds write in Microsoft Office Excel allows attackers to execute code locally after required user interaction. The published record does not identify the input that reaches the faulty write or the affected Excel routine. Successful exploitation runs code in the user's context and can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2026-68806
- Published
- Aug 11, 2026
- Updated
- Aug 25, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2024
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 11, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 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.112.26081010
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.
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