CVE-2025-62216

7.8

Microsoft · Office

A use after free vulnerability in Microsoft Office allows an unauthorized attacker to execute arbitrary code locally on the target system.

Executive summary

A critical use after free vulnerability in Microsoft Office products permits local code execution by an unauthorized attacker, posing a significant risk to system integrity.

Vulnerability

This is a use after free flaw (CWE-416) within Microsoft Office, which can be triggered by an unauthorized attacker to achieve local code execution. The attack vector is local with low complexity, though it typically requires user interaction.

Business impact

Successful exploitation of this vulnerability allows an attacker to execute code with the privileges of the logged-in user, potentially leading to full system compromise. With a CVSS score of 7.8, this flaw represents a high-severity risk that could result in unauthorized data access, the installation of malicious software, or persistent unauthorized presence within the organizational environment.

Remediation

Immediate Action: Organizations must apply the latest security updates provided by Microsoft via the official Office Security Releases portal immediately.

Proactive Monitoring: Security teams should monitor endpoint logs for suspicious child processes spawned by Office applications, such as unexpected command shells or PowerShell execution.

Compensating Controls: Implement robust endpoint detection and response (EDR) solutions to identify and block malicious memory manipulation attempts or abnormal process behavior associated with office document handling.

Exploitation status

Public Exploit Available: No — exploit_available (false).

Analyst recommendation

Given the severity of potential code execution, administrators should prioritize the deployment of the vendor-supplied patches to all affected Microsoft Office installations. Ensure that automated update mechanisms are functioning correctly and verify that all enterprise endpoints are running the most recent version of the software to mitigate this risk.

More Microsoft CVEs

Sources