Code execution via use-after-free
Published Nov 12, 2024 · Updated Jul 8, 2025
Use-after-free in Microsoft Excel allows context-dependent attackers to execute code when a user opens a crafted local file. Microsoft identifies the weakness as use-after-free but has not disclosed the affected code locus or the lifetime operation that leaves an object accessible after release. Exploitation requires user interaction with the file, and successful code runs in the user's security context with confidentiality, integrity, and availability impact.
Summary
What happened
Use-after-free in Microsoft Excel allows context-dependent attackers to execute code when a user opens a crafted local file. Microsoft identifies the weakness as use-after-free but has not disclosed the affected code locus or the lifetime operation that leaves an object accessible after release. Exploitation requires user interaction with the file, and successful code runs in the user's security context with confidentiality, integrity, and availability impact.
The record
- CVE
- CVE-2024-49027
- Published
- Nov 12, 2024
- Updated
- Jul 8, 2025
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2024
- Classifications
- CWE-416, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 12, 2024CVE publishedPublication date reported by the CVE source.
- Jul 8, 2025Record 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=1.0.0 <16.91.24111020
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