Code execution via stack-based overflow
Published Aug 11, 2026 · Updated Aug 25, 2026
Stack-based buffer overflow in Microsoft Office Excel before August 2026 updates allows attackers to execute code locally via a crafted file. Microsoft has not disclosed the affected parser, file format, or code path beyond classifying the flaw as a stack-based buffer overflow in Excel. The published CVSS vector indicates a local, user-assisted trigger, so the practical consequence is code execution in the Office process after malicious content is opened rather than a documented network-reachable compromise path.
Summary
What happened
Stack-based buffer overflow in Microsoft Office Excel before August 2026 updates allows attackers to execute code locally via a crafted file. Microsoft has not disclosed the affected parser, file format, or code path beyond classifying the flaw as a stack-based buffer overflow in Excel. The published CVSS vector indicates a local, user-assisted trigger, so the practical consequence is code execution in the Office process after malicious content is opened rather than a documented network-reachable compromise path.
The record
- CVE
- CVE-2026-68817
- Published
- Aug 11, 2026
- Updated
- Aug 25, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-121, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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