Code execution via double-free memory corruption
Published Sep 8, 2026 · Updated Sep 9, 2026
Double-free memory corruption in Microsoft Office Excel allows attackers to execute code locally after a user opens a crafted file. Microsoft identifies Excel as the affected component but does not disclose the allocation or parsing routine that frees the same memory twice. Exploitation requires user interaction and yields code execution in the user's security context; no remote service is exposed.
Summary
What happened
Double-free memory corruption in Microsoft Office Excel allows attackers to execute code locally after a user opens a crafted file. Microsoft identifies Excel as the affected component but does not disclose the allocation or parsing routine that frees the same memory twice. Exploitation requires user interaction and yields code execution in the user's security context; no remote service is exposed.
The record
- CVE
- CVE-2026-81950
- Published
- Sep 8, 2026
- Updated
- Sep 9, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2024
- Classifications
- CWE-415, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 8, 2026CVE publishedPublication date reported by the CVE source.
- Sep 9, 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=-
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