Here is a complete breakdown of the vulnerability mechanics, risk metrics, affected Office channels, and exact build targets administrators need to verify across their environments.
Vulnerability Overview and Risk Metrics
At its core, CVE-2026-81957 stems from a classic memory-handling defect classified under CWE-125 (out-of-bounds read). As stated in the official MSRC description: Out-of-bounds read in Microsoft Office Excel allows an unauthorized attacker to execute code locally. MSRC's advisory summary reinforces this exact scope under Microsoft Office Excel Remote Code Execution Vulnerability: an out-of-bounds read in Microsoft Office Excel allows an unauthorized attacker to execute code locally.
From a general software security perspective, out-of-bounds reads occur when a program reads memory past the boundaries of an allocated buffer. Although reading out-of-bounds memory is frequently associated with information disclosure or application crashes, complex document parsers that use read values to calculate pointers, object offsets, or subsequent control-flow operations can turn an out-of-bounds read into arbitrary code execution within the context of the current user.
Microsoft has assigned the following official risk ratings and status indicators to CVE-2026-81957:
- CVE ID: CVE-2026-81957
- Title: Microsoft Excel Remote Code Execution Vulnerability
- Severity: Important
- CVSS Base Score: 7.8
- CVSS Temporal Score: 6.8
- CVSS Vector:
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C - Weakness (CWE): CWE-125
- Exploitation Assessment: Exploitation Less Likely
- Publicly disclosed: No
- Exploited: No
- Customer action required: Yes
Section Summary: CVE-2026-81957 is an Important-severity CWE-125 out-of-bounds read carrying a 7.8 base score and 6.8 temporal score. While active exploitation has not been observed and Microsoft rates exploitation as less likely, customer patching is required to close the flaw.
Attack Vector and Real-World Exposure
Why does a vulnerability titled "Remote Code Execution" carry a Local Attack Vector (AV:L) in its CVSS string (CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C)? In CVSS v3.1 scoring, vulnerabilities triggered by opening a malicious file locally—even when that file arrives from across the internet via email or chat—are scored with AV:L and User Interaction Required (UI:R).
Two official MSRC advisory clarifications define the exact operational risk for defenders:
- No Preview Pane exposure: Is the Preview Pane an attack vector for this vulnerability? No, the Preview Pane is not an attack vector. Merely viewing or highlighting a malicious attachment in a mail or file preview pane will not trigger the flaw.
- Required user interaction (
UI:R): According to the CVSS metric, user interaction is required (UI:R). An attacker must send a user a malicious Office file and convince them to open it.
Because low attack complexity (AC:L) and zero privileges (PR:N) are paired with high confidentiality, integrity, and availability impacts (C:H/I:H/A:H), social engineering is the primary gatekeeper. Consider a routine finance department workflow: invoices, budget trackers, and vendor schedules arrive daily as spreadsheet attachments. If a persuasive phishing lure convinces an employee on an unpatched machine to open a crafted Office file, the attacker gains code execution with the same local permissions as that user—without needing the Preview Pane or pre-existing credentials. Conversely, the temporal vector components (E:U/RL:O/RC:C) reflect unproven exploit maturity alongside an official vendor fix and confirmed report confidence, bringing the temporal score down to 6.8.
Section Summary: Attackers cannot trigger CVE-2026-81957 through the Preview Pane alone; they must deliver a malicious Office file and persuade a user to open it.
Affected Products, KB Articles, and Fixed Builds
This advisory spans legacy MSI-installed 2016 packages (which require standalone Knowledge Base updates), Click-to-Run perpetual and subscription channels on x86 and x64 architectures, and Mac releases. Notably, MSRC specifically confirms Mac patch availability in its advisory FAQ: as of September 16, 2026, the security updates for Microsoft Office LTSC for Mac 2021, Microsoft Office LTSC for Mac 2024, and Microsoft Office 365 for Mac are available, and 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.
| Affected Product | KB Article | Vendor Fixed Build |
|---|---|---|
| Microsoft 365 Apps for Enterprise for 32-bit Systems (x86) | Not applicable (Click-to-Run) | 16.0.20326.20138 |
| Microsoft 365 Apps for Enterprise for 64-bit Systems (x64) | Not applicable (Click-to-Run) | 16.0.20326.20138 |
| Microsoft Excel 2016 (32-bit edition) (x86) | KB5002914 | 16.0.5569.1003 |
| Microsoft Excel 2016 (64-bit edition) (x64) | KB5002914 | 16.0.5569.1003 |
| Microsoft Office 2016 (32-bit edition) (x86) | KB5002904 | 16.0.5569.1003 |
| Microsoft Office 2016 (64-bit edition) (x64) | KB5002904 | 16.0.5569.1003 |
| Microsoft Office 2019 for 32-bit editions (x86) | Not applicable (Click-to-Run) | 16.0.10417.20207 |
| Microsoft Office 2019 for 64-bit editions (x64) | Not applicable (Click-to-Run) | 16.0.10417.20207 |
| Microsoft Office 365 for Mac | Not applicable (Mac update) | 16.113.26091433 |
| Microsoft Office LTSC 2021 for 32-bit editions (x86) | Not applicable (Click-to-Run) | 16.0.14334.20906 |
| Microsoft Office LTSC 2021 for 64-bit editions (x64) | Not applicable (Click-to-Run) | 16.0.14334.20906 |
| Microsoft Office LTSC 2024 for 32-bit editions (x86) | Not applicable (Click-to-Run) | 16.0.17932.20976 |
| Microsoft Office LTSC 2024 for 64-bit editions (x64) | Not applicable (Click-to-Run) | 16.0.17932.20976 |
| Microsoft Office LTSC for Mac 2021 | Not applicable (Mac update) | 16.113.26091433 |
| Microsoft Office LTSC for Mac 2024 | Not applicable (Mac update) | 16.113.26091433 |
Pay close attention to the 2016 editions: organizations still maintaining 2016 installations must ensure both the core suite update (KB5002904) and the Excel-specific update (KB5002914) are accounted for where applicable so binaries reach build 16.0.5569.1003.
Section Summary: Fifteen distinct product entries across 32-bit, 64-bit, and Mac platforms require updates, with 2016 editions relying on KB5002904 and KB5002914 and newer releases updating directly by build number.
Official Remediation Checklist for Administrators
To bring all endpoints into compliance, apply the exact vendor remediation actions corresponding to each deployed edition:
- 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 Excel 2016 (32-bit edition) (x86), install KB5002914 to reach fixed build 16.0.5569.1003.
- For Microsoft Excel 2016 (64-bit edition) (x64), install KB5002914 to reach fixed build 16.0.5569.1003.
- For Microsoft Office 2016 (32-bit edition) (x86), install KB5002904 to reach fixed build 16.0.5569.1003.
- For Microsoft Office 2016 (64-bit edition) (x64), install KB5002904 to reach fixed build 16.0.5569.1003.
- 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.
From an operational standpoint, based on general IT administration practice, IT teams should verify installed Office build numbers directly through endpoint inventory queries rather than assuming automatic Click-to-Run or Mac auto-update channels have completed—especially on laptops that stay suspended or off corporate networks, where background Office updates often wait until the application restarts. For ongoing discussions on enterprise patch management and Microsoft security advisories, check out our dedicated security and Office administration sections right here on WindowsForum.com.
Section Summary: Administrators must confirm that every Office installation meets or exceeds its respective fixed build—ranging from 16.0.5569.1003 via KB5002904 and KB5002914 on 2016 releases to 16.0.20326.20138 on Microsoft 365 Apps for Enterprise and 16.113.26091433 on Mac editions.
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