Local code execution via double-free memory corruption
Published Jul 14, 2026 · Updated Jul 14, 2026
A double-free flaw in Microsoft Office Word allows local users to execute arbitrary code after a user opens a crafted document. Word releases the same memory allocation twice during document processing, but Microsoft has not disclosed the affected parser, file structure, or function. Exploitation requires user interaction and yields code execution in the security context of the user who opens the document.
Summary
What happened
A double-free flaw in Microsoft Office Word allows local users to execute arbitrary code after a user opens a crafted document. Word releases the same memory allocation twice during document processing, but Microsoft has not disclosed the affected parser, file structure, or function. Exploitation requires user interaction and yields code execution in the security context of the user who opens the document.
The record
- CVE
- CVE-2026-55132
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2024
- Classifications
- CWE-415, T1203, T1204.002
- 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.
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