While document-borne threats often trigger immediate alarm in security operations centers, the technical contours of CVE-2026-78521 offer both a clear warning and some welcome breathing room. MSRC explicitly defines the core flaw: Heap-based buffer overflow in Microsoft Office Word allows an unauthorized attacker to execute code over a network. Even so, turning that flaw into a working compromise takes more than simply dropping an attachment into a target's inbox. Let us unpack what the official telemetry tells us, how the attack chain operates, and which exact builds lock the door.
Advisory Snapshot and Official Telemetry
Before diving into deployment mechanics, IT teams need the hard numbers and official status indicators from the MSRC advisory to calibrate their patching schedules:
- CVE Identifier: CVE-2026-78521
- Vulnerability Title: Microsoft Office Word Remote Code Execution Vulnerability
- Severity: Important
- CVSS Base Score: 8.8
- CVSS Temporal Score: 7.7
- CVSS Vector:
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C - Weakness Classification: CWE-122 (Heap-based Buffer Overflow)
- Exploitation Assessment: Exploitation Less Likely
- Publicly disclosed: No
- Exploited: No
- Customer action required: Yes
From a general industry risk-management perspective, pairing an 8.8 base score with an Important (rather than Critical) severity rating comes down to user interaction. Decoding the official vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C) tells the whole story. The attack vector is network-based (AV:N), attack complexity is low (AC:L), and privileges required are none (PR:N), meaning an unauthenticated outsider can craft and send the payload. However, UI:R confirms that user interaction is mandatory, while S:U shows the scope remains unchanged—successful code execution runs within the security context of the logged-in user, carrying high impact across confidentiality, integrity, and availability (C:H/I:H/A:H). Temporal modifiers (E:U/RL:O/RC:C) reflect unproven exploit maturity, an official fix, and confirmed report confidence, bringing the temporal score to 7.7.
Section Summary: CVE-2026-78521 carries high technical impact if triggered, though the lack of active exploitation and the requirement for multi-step user action keep its MSRC assessment at Exploitation Less Likely.
Anatomy of the Mail-Merge Attack Vector
How does a classic memory bug manifest inside a modern word processor? Tracked under CWE-122, a heap-based buffer overflow happens when an application allocates a fixed chunk of dynamically managed heap memory to hold incoming data—such as structured fields or record buffers—and then writes past that boundary without adequate length validation. When untrusted input overwrites adjacent heap metadata or function pointers, a crash can be steered into arbitrary code execution.
MSRC's official advisory details the exact operational scenario and rules out zero-click exposure:
- Attack Mechanics: How could an attacker exploit this vulnerability? An attacker could send a specially crafted Word document containing malicious mail-merge data to a target user. The user would need to open the document and process or update the mail-merge data. Successful exploitation could allow the attacker to execute code on the user's system. Authentication is not required.
- Preview Pane Risk: Is the Preview Pane an attack vector for this vulnerability? No, the Preview Pane is not an attack vector.
- Core Vulnerability Summary: Microsoft Office Word Remote Code Execution Vulnerability: Heap-based buffer overflow in Microsoft Office Word allows an unauthorized attacker to execute code over a network.
For enterprise defenders, that Preview Pane confirmation is a major relief. Historically, vulnerabilities triggered merely by rendering a file in Outlook's reading pane or Windows File Explorer have treated patch teams to sleepless nights because users do not even have to click twice to get burned. Here, simply viewing a document thumbnail or reading its static text in a preview window will not trigger the faulty code path.
That said, why should administrators avoid complacency? Consider who actually uses mail merge on a Tuesday morning. Marketing coordinators, legal assistants, school administrators, and accounts-payable clerks routinely open external templates and refresh linked mail-merge data sources as part of their daily jobs. If a socially engineered lure arrives disguised as an updated vendor mailing template or event roster, asking the recipient to open the file and update the mail-merge fields blends right into normal business workflows.
Section Summary: Merely previewing a malicious file will not trigger CVE-2026-78521; a user must open the crafted document and actively process or update its mail-merge data for the CWE-122 heap overflow to execute code.
Affected Products, Builds, and Mac Update Timing
The scope of CVE-2026-78521 spans thirteen distinct product entries across subscription builds, Long-Term Servicing Channel (LTSC) releases, retail/volume editions on Windows, standalone MSI installations, and Mac deployments. Notably, MSRC highlights specific availability details for Apple desktop fleets in its advisory guidance:
- Mac Update Status: Are the updates for Microsoft Office LTSC for Mac 2021 and 2024 currently available? Yes. As of September 16, 2026, the security update for Microsoft Office LTSC for Mac 2021, 2024 and Microsoft Office 365 for Mac are available. Customers running Microsoft Office LTSC for Mac 2021, 2024 and Microsoft Office 365 for Mac should ensure the update is installed to be protected from this vulnerability.
Across the broader ecosystem documented by MSRC, Microsoft Office security update release notes, and Microsoft Support, modern Click-to-Run and Mac editions transition directly to updated build numbers, whereas MSI-based Word 2016 deployments apply a standalone Knowledge Base package (KB5002923).
| Affected Product | Update Mechanism / KB | Vendor Fixed Build |
|---|---|---|
| Microsoft 365 Apps for Enterprise for 32-bit Systems (x86) | Build update | 16.0.20326.20138 |
| Microsoft 365 Apps for Enterprise for 64-bit Systems (x64) | Build update | 16.0.20326.20138 |
| Microsoft Office 2019 for 32-bit editions (x86) | Build update | 16.0.10417.20207 |
| Microsoft Office 2019 for 64-bit editions (x64) | Build update | 16.0.10417.20207 |
| Microsoft Office 365 for Mac | Build update | 16.113.26091433 |
| Microsoft Office LTSC 2021 for 32-bit editions (x86) | Build update | 16.0.14334.20906 |
| Microsoft Office LTSC 2021 for 64-bit editions (x64) | Build update | 16.0.14334.20906 |
| Microsoft Office LTSC 2024 for 32-bit editions (x86) | Build update | 16.0.17932.20976 |
| Microsoft Office LTSC 2024 for 64-bit editions (x64) | Build update | 16.0.17932.20976 |
| Microsoft Office LTSC for Mac 2021 | Build update | 16.113.26091433 |
| Microsoft Office LTSC for Mac 2024 | Build update | 16.113.26091433 |
| Microsoft Word 2016 (32-bit edition) (x86) | KB5002923 | 16.0.5569.1000 |
| Microsoft Word 2016 (64-bit edition) (x64) | KB5002923 | 16.0.5569.1000 |
Section Summary: Every supported generation of Office from legacy Word 2016 through LTSC 2024 and subscription releases on Windows and Mac requires updating to its corresponding fixed build.
Official Remediation Checklist and Verification Guidance
Because Customer action required: Yes applies to this release, system administrators managing mixed endpoint estates should verify that automated update channels have actually converged on the patched builds—especially on laptops that spend weeks hibernating in backpacks or VDI gold images waiting for maintenance windows. Follow the exact official remediation targets below for every edition in your inventory:
- For Microsoft 365 Apps for Enterprise for 32-bit Systems (x86), update to fixed build 16.0.20326.20138 or later.
- For Microsoft 365 Apps for Enterprise for 64-bit Systems (x64), update to fixed build 16.0.20326.20138 or later.
- For Microsoft Office 2019 for 32-bit editions (x86), update to fixed build 16.0.10417.20207 or later.
- For Microsoft Office 2019 for 64-bit editions (x64), update to fixed build 16.0.10417.20207 or later.
- For Microsoft Office 365 for Mac, update to fixed build 16.113.26091433 or later.
- For Microsoft Office LTSC 2021 for 32-bit editions (x86), update to fixed build 16.0.14334.20906 or later.
- For Microsoft Office LTSC 2021 for 64-bit editions (x64), update to fixed build 16.0.14334.20906 or later.
- For Microsoft Office LTSC 2024 for 32-bit editions (x86), update to fixed build 16.0.17932.20976 or later.
- For Microsoft Office LTSC 2024 for 64-bit editions (x64), update to fixed build 16.0.17932.20976 or later.
- For Microsoft Office LTSC for Mac 2021, update to fixed build 16.113.26091433 or later.
- For Microsoft Office LTSC for Mac 2024, update to fixed build 16.113.26091433 or later.
- For Microsoft Word 2016 (32-bit edition) (x86), install KB5002923 to reach fixed build 16.0.5569.1000.
- For Microsoft Word 2016 (64-bit edition) (x64), install KB5002923 to reach fixed build 16.0.5569.1000.
Based on standard IT administration practice, there are two common operational blind spots worth checking when rolling out Microsoft security patches like these:
- Restarting Open Office Apps: Click-to-Run updates stage silently in the background on Windows PCs, yet they cannot finalize file replacements while Word or Outlook processes remain open. Remind users who treat reboots like an annual holiday to close their Office apps so the new build actually takes effect.
- Cross-Platform Parity: It is all too easy for Windows-focused patch teams to verify Click-to-Run compliance and KB5002923 rollout while overlooking executive or creative-team Macs. Confirm that Microsoft AutoUpdate policies on macOS have brought Microsoft Office 365 for Mac, Microsoft Office LTSC for Mac 2021, and Microsoft Office LTSC for Mac 2024 up to build
16.113.26091433or later.
For ongoing discussion around enterprise patch verification, Office LTSC servicing strategies, and document security hardening, check out our dedicated security and Office administration discussions right here on WindowsForum.com.
Section Summary: Closing out CVE-2026-78521 is straightforward once endpoints pull their designated Click-to-Run builds, Mac updates (16.113.26091433), or MSI patch (KB5002923)—provided administrators confirm that pending app restarts have completed across both Windows and Mac fleets.
References
- Official MSRC or vendor evidence msrc.microsoft.com
- Official MSRC or vendor evidence api.msrc.microsoft.com
- Official MSRC or vendor evidence api.msrc.microsoft.com