Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Remote Code Execution in Microsoft Office Out-of-Bounds Read

IdentifiersCVE-2025-49696CWE-125· Out-of-bounds Read

CVE-2025-49696 is a Critical Microsoft Office vulnerability described by Microsoft as an out-of-bounds read that can lead to remote code execution. Supporting content also associates the issue with a heap-based buffer overflow condition. Microsoft states that an unauthorized attacker can execute code locally, while clarifying that the overall security impact is remote code execution/arbitrary code execution. The CVSS 3.1 vector is AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H with a base score of 8.4. The vulnerability affects Microsoft Office, including Windows editions and Mac editions such as Microsoft Office LTSC for Mac 2021 and 2024. The Preview Pane is confirmed as an attack vector, and multiple sources in the provided content state exploitation can occur without user interaction.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows arbitrary code execution in the context of the affected local machine. The resulting impact is high across confidentiality, integrity, and availability, enabling an attacker to run code, access or modify data available to the compromised Office process or host context, and potentially disrupt system operation. Microsoft assessed exploitation as more likely, although the vulnerability was not publicly disclosed and not known to be exploited in the wild at initial publication time.

Mitigation

If you can’t patch tonight, do this now.

No vendor workaround is provided in the supplied content. Until patches are fully deployed, reduce exposure to untrusted Office documents and attachment content, especially in workflows where the Preview Pane is enabled. Use compensating controls such as email and attachment filtering, restrict or avoid previewing untrusted files, and prioritize patch deployment on systems that process externally sourced Office content.

Remediation

Patch, then assume compromise.

Apply Microsoft's security updates for all affected Microsoft Office products. The provided advisory content specifically states that updates for Microsoft Office LTSC for Mac 2021 and 2024 were available as of 2025-07-15 and should be installed to be protected from this vulnerability. Prioritize patching because Microsoft rated the issue Critical and assessed exploitation as more likely.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft Corporation365 Appsapplication
Microsoft Corporation365 Copilotapplication
Microsoft CorporationOfficeapplication
Microsoft CorporationOffice 2016application
Microsoft CorporationOffice 2019application
Microsoft CorporationOffice 2021application
Microsoft CorporationOffice 2024application
Microsoft CorporationOffice Long Term Servicing Channelapplication
Microsoft CorporationOffice Macos 2021application
Microsoft CorporationOffice Macos 2024application

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity

Community discussion across Reddit, Mastodon, and other social sources.