Local code execution via use-after-free memory access
Published Aug 12, 2025 · Updated Feb 13, 2026
Use-after-free memory corruption in Microsoft Office allows attackers to execute code locally without prior authentication. Microsoft identifies the flaw only as a use-after-free in Office and has not disclosed the affected component, freed object, or triggering input. Exploitation requires local attack placement but no privileges or user interaction, and successful code execution can read, alter, or disrupt data in the current user's security context.
Summary
What happened
Use-after-free memory corruption in Microsoft Office allows attackers to execute code locally without prior authentication. Microsoft identifies the flaw only as a use-after-free in Office and has not disclosed the affected component, freed object, or triggering input. Exploitation requires local attack placement but no privileges or user interaction, and successful code execution can read, alter, or disrupt data in the current user's security context.
The record
- CVE
- CVE-2025-53740
- Published
- Aug 12, 2025
- Updated
- Feb 13, 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 13, 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