Code execution via stack-based buffer overflow
Published Mar 11, 2025 · Updated Feb 13, 2026
Stack-based buffer overflow in Microsoft Office Excel allows attackers to execute code when a user opens a crafted file. Microsoft identifies Excel's stack-based buffer handling as the faulty locus but has not disclosed the parser, function, or unchecked input that overruns the stack. Exploitation requires local processing and user interaction, and successful exploitation runs attacker-controlled code.
Summary
What happened
Stack-based buffer overflow in Microsoft Office Excel allows attackers to execute code when a user opens a crafted file. Microsoft identifies Excel's stack-based buffer handling as the faulty locus but has not disclosed the parser, function, or unchecked input that overruns the stack. Exploitation requires local processing and user interaction, and successful exploitation runs attacker-controlled code.
The record
- CVE
- CVE-2025-24075
- Published
- Mar 11, 2025
- Updated
- Feb 13, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2024
- Classifications
- CWE-121, T1203, T1204.002
- 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.
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