Code execution via invalid non-heap memory release
Published Sep 9, 2025 · Updated Sep 9, 2025
CWE-590 memory-management flaw in Microsoft Excel allows attackers to execute code locally after required user interaction. Excel attempts to free memory that was not allocated on the heap, but Microsoft has not identified the responsible parser or function. Successful exploitation runs code in the affected user's security context and can affect data and availability.
Summary
What happened
CWE-590 memory-management flaw in Microsoft Excel allows attackers to execute code locally after required user interaction. Excel attempts to free memory that was not allocated on the heap, but Microsoft has not identified the responsible parser or function. Successful exploitation runs code in the affected user's security context and can affect data and availability.
The record
- CVE
- CVE-2025-54899
- Published
- Sep 9, 2025
- Updated
- Sep 9, 2025
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2024
- Classifications
- CWE-590, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 9, 2025CVE publishedPublication date reported by the CVE source.
- Sep 9, 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=N/A
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