Code execution via crafted-file heap overflow
Published Mar 11, 2025 · Updated Feb 13, 2026
Heap-based buffer overflow in Microsoft Office allows context-dependent attackers to execute code by opening a crafted file. Microsoft identifies the affected component only as Office and has not published the parser, file format, or memory-copy operation that overruns the heap buffer. Exploitation requires a user to open the crafted file, after which code runs with that user's privileges and can read, alter, or interrupt resources available to the Office process.
Summary
What happened
Heap-based buffer overflow in Microsoft Office allows context-dependent attackers to execute code by opening a crafted file. Microsoft identifies the affected component only as Office and has not published the parser, file format, or memory-copy operation that overruns the heap buffer. Exploitation requires a user to open the crafted file, after which code runs with that user's privileges and can read, alter, or interrupt resources available to the Office process.
The record
- CVE
- CVE-2025-24057
- Published
- Mar 11, 2025
- Updated
- Feb 13, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2024
- Classifications
- CWE-122, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 11, 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.95.25030928
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