Code execution via undisclosed heap buffer overflow
Published May 12, 2026 · Updated May 12, 2026
Heap-based buffer overflow in Microsoft Office for Android and Mac allows attackers to execute code after user interaction. Microsoft has not disclosed the affected Office component, the input that overruns its heap buffer, or the faulty memory operation. Execution requires a local attack path and user interaction, and successful exploitation grants code execution in the affected user's context.
Summary
What happened
Heap-based buffer overflow in Microsoft Office for Android and Mac allows attackers to execute code after user interaction. Microsoft has not disclosed the affected Office component, the input that overruns its heap buffer, or the faulty memory operation. Execution requires a local attack path and user interaction, and successful exploitation grants code execution in the affected user's context.
The record
- CVE
- CVE-2026-42831
- Published
- May 12, 2026
- Updated
- May 12, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2024
- Classifications
- CWE-122, T1204
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2026CVE publishedPublication date reported by the CVE source.
- May 12, 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.109.26051019
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