Quick answers
- Is CVE-2025-49697 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-49697 being exploited in the wild.
- How severe is CVE-2025-49697?
- High severity, with a CVSS score of 8.4, published 8 July 2025.
- Which products and versions are affected?
- Microsoft Office Online Server up to (excluding) 16.0.10417.20027.
- Is there a fix for CVE-2025-49697?
- 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-49697 attacked?
- It is attacked with local access, in a network appliance.
- Am I affected by CVE-2025-49697?
- 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 heap-based buffer overflow (CWE-122) exists in multiple versions of Microsoft Office, including Office 2016, 2019, LTSC 2021/2024, and Microsoft 365 Apps. The vulnerability is triggered when the application improperly handles data in memory, allowing an attacker to overwrite adjacent memory locations. Although the attack vector is classified as local, a successful exploit allows for arbitrary code execution with the privileges of the logged-in user. The vulnerability affects various platforms including Windows, macOS, and Android. Microsoft has released security updates to address this issue.
Affected products
- Microsoft Office 2016
- Microsoft Office 2019
- Microsoft Office LTSC 2021
- Microsoft Office LTSC 2024
- Microsoft 365 Apps for Enterprise
- Microsoft Office Online Server up to (excluding) 16.0.10417.20027
- Microsoft Office for Android
Timeline
- 2025-07-08: disclosed: Initial disclosure by Microsoft
- 2025-07-08: advisory: Microsoft MSRC advisory published