Is CVE-2025-47167 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2025-47167 being exploited in the wild.

How severe is CVE-2025-47167?

High severity, with a CVSS score of 8.4, published 10 June 2025.

Which products and versions are affected?

Microsoft 365 Copilot Android versions prior to 16.0.18925.20000; Microsoft Office 2016, 2019, LTSC 2021, LTSC 2024, 365 Apps for Enterprise, Android versions prior to 16.0.18925.20000.

Is there a fix for CVE-2025-47167?

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-47167 attacked?

It is attacked with local access, in a network appliance.

Am I affected by CVE-2025-47167?

Check whether you run Microsoft 365 Copilot or Microsoft Office 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.

CVE-2025-47167: Microsoft Office type confusion code execution

CVE-2025-47167 · Severity: high · CVSS 8.4 · Published 2025-06-10

A vulnerability in Microsoft Office could allow an attacker to execute malicious code on a user's device. This issue affects various versions of Office across Windows, macOS, and Android, potentially leading to full system compromise or unauthorized data access. To exploit this, an attacker would typically need to have a presence on the local system or trick a user into running a malicious file.

Technologies: Microsoft 365 Copilot, Microsoft Office. Vendors: Microsoft.

Quick answers

Is CVE-2025-47167 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2025-47167 being exploited in the wild.
How severe is CVE-2025-47167?: High severity, with a CVSS score of 8.4, published 10 June 2025.
Which products and versions are affected?: Microsoft 365 Copilot Android versions prior to 16.0.18925.20000; Microsoft Office 2016, 2019, LTSC 2021, LTSC 2024, 365 Apps for Enterprise, Android versions prior to 16.0.18925.20000.
Is there a fix for CVE-2025-47167?: 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-47167 attacked?: It is attacked with local access, in a network appliance.
Am I affected by CVE-2025-47167?: Check whether you run Microsoft 365 Copilot or Microsoft Office 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 type confusion vulnerability (CWE-843) exists in Microsoft Office due to the application accessing resources using an incompatible type. This flaw allows an attacker to bypass memory safety protections and execute arbitrary code in the context of the current user. The attack vector is local, meaning the attacker must already have a foothold on the system or deliver a malicious payload that is executed locally. The vulnerability impacts a wide range of products including Office 2016, 2019, LTSC versions, and Microsoft 365 Apps. Microsoft has released security updates to address this issue; users should update to the latest available versions, such as Android version 16.0.18925.20000 or later.

Affected products

Microsoft Office 2016, 2019, LTSC 2021, LTSC 2024, 365 Apps for Enterprise, Android versions prior to 16.0.18925.20000
Microsoft 365 Copilot Android versions prior to 16.0.18925.20000

Timeline

2025-06-10: disclosed
2025-06-10: advisory

References

https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-47167

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.