Quick answers
- Is CVE-2025-59227 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-59227 being exploited in the wild.
- How severe is CVE-2025-59227?
- High severity, with a CVSS score of 7.8, published 14 October 2025.
- Which products and versions are affected?
- Microsoft Office for Android versions prior to 16.0.19328.20000.
- Is there a fix for CVE-2025-59227?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-59227 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2025-59227?
- Check whether you run Microsoft 365 Apps for Enterprise, Microsoft Office 2016, Microsoft Office 2019 or one of the others listed at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A use-after-free (CWE-416) vulnerability exists in multiple versions of Microsoft Office, including desktop and Android editions. The flaw is triggered when the application continues to use a pointer after it has been freed, leading to memory corruption. An attacker can exploit this by convincing a user to open a malicious file, resulting in local code execution with the privileges of the current user. The attack vector is local with a requirement for user interaction (UI:R). Microsoft has released security updates to address this issue across affected platforms.
Affected products
- Microsoft Office 2016
- Microsoft Office 2019
- Microsoft Office LTSC 2021
- Microsoft Office LTSC 2024
- Microsoft 365 Apps for Enterprise
- Microsoft Office for Android versions prior to 16.0.19328.20000
Timeline
- 2025-10-14: disclosed
- 2025-10-14: advisory: MSRC advisory published