Code execution via heap-based buffer overflow
Published Jul 14, 2026 · Updated Jul 14, 2026
Heap-based buffer overflow in Microsoft Office Word allows attackers to execute code when a user opens crafted content. Microsoft has not disclosed the affected parser, buffer sizing operation, or crafted input format that causes the heap overwrite. Successful exploitation requires user interaction and runs code in the context of the affected Office or SharePoint process.
Summary
What happened
Heap-based buffer overflow in Microsoft Office Word allows attackers to execute code when a user opens crafted content. Microsoft has not disclosed the affected parser, buffer sizing operation, or crafted input format that causes the heap overwrite. Successful exploitation requires user interaction and runs code in the context of the affected Office or SharePoint process.
The record
- CVE
- CVE-2026-55127
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2024
- Classifications
- CWE-122, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 14, 2026CVE publishedPublication date reported by the CVE source.
- Jul 14, 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.111.26071215
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