Local code execution via use-after-free
Published Aug 12, 2025 · Updated Feb 26, 2026
Use-after-free in Microsoft Office allows local users to execute arbitrary code through an unspecified local attack vector. Microsoft identifies the affected component only as the Office suite and has not disclosed the object lifetime error, triggering input, or code path that accesses freed memory. Exploitation requires local access but no privileges or user interaction, and successful code execution can compromise confidentiality, integrity, and availability.
Summary
What happened
Use-after-free in Microsoft Office allows local users to execute arbitrary code through an unspecified local attack vector. Microsoft identifies the affected component only as the Office suite and has not disclosed the object lifetime error, triggering input, or code path that accesses freed memory. Exploitation requires local access but no privileges or user interaction, and successful code execution can compromise confidentiality, integrity, and availability.
The record
- CVE
- CVE-2025-53731
- Published
- Aug 12, 2025
- Updated
- Feb 26, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2024
- Classifications
- CWE-416, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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.100.25081015
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