Code execution via type-confused resource access
Published Jul 14, 2026 · Updated Jul 14, 2026
Type confusion in Microsoft Office Excel allows remote attackers to execute code locally after a user opens a crafted file. Excel accesses a resource using an incompatible type, but Microsoft has not disclosed the affected parser, object, or unsafe operation. Exploitation requires user interaction and can run attacker-controlled code in the user's security context on affected Windows and macOS clients or through Office Online Server document processing.
Summary
What happened
Type confusion in Microsoft Office Excel allows remote attackers to execute code locally after a user opens a crafted file. Excel accesses a resource using an incompatible type, but Microsoft has not disclosed the affected parser, object, or unsafe operation. Exploitation requires user interaction and can run attacker-controlled code in the user's security context on affected Windows and macOS clients or through Office Online Server document processing.
The record
- CVE
- CVE-2026-55025
- Published
- Jul 14, 2026
- Updated
- Jul 14, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2024
- Classifications
- CWE-843, 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