Local code execution via out-of-bounds read
Published Aug 11, 2026 · Updated Aug 25, 2026
Out-of-bounds read in Microsoft Office allows attackers to execute code locally via a crafted Office file opened on a target system. Microsoft has disclosed only that Office reads past an intended buffer boundary, and the published advisories do not identify the parser, file format, or code path that mishandles untrusted input. Exploitation requires local access and user interaction to open a malicious document, and successful exploitation runs code with the rights of the user who opened it.
Summary
What happened
Out-of-bounds read in Microsoft Office allows attackers to execute code locally via a crafted Office file opened on a target system. Microsoft has disclosed only that Office reads past an intended buffer boundary, and the published advisories do not identify the parser, file format, or code path that mishandles untrusted input. Exploitation requires local access and user interaction to open a malicious document, and successful exploitation runs code with the rights of the user who opened it.
The record
- CVE
- CVE-2026-63515
- Published
- Aug 11, 2026
- Updated
- Aug 25, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-191, CWE-125, 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