While Microsoft rates the vulnerability Important rather than Critical—largely because an attacker needs valid credentials before knocking on the door—the underlying CVSS base score of 8.8 and temporal score of 7.7 tell a clear operational story. Once inside the perimeter with even modest permissions, an adversary could leverage this weakness without waiting for a single user to click a link or open a file.
Advisory Breakdown and Core Metrics
For patch management teams triaging their deployment queues, having the exact MSRC telemetry in one place makes risk scoring straightforward. Below is the complete breakdown of the official advisory data for CVE-2026-109464:
| Advisory Field | Official Value |
|---|---|
| CVE Identifier | CVE-2026-109464 |
| Vulnerability Title | Microsoft Office SharePoint Remote Code Execution Vulnerability |
| Severity Rating | Important |
| CVSS Base Score | 8.8 |
| CVSS Temporal Score | 7.7 |
| CVSS Vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C |
| Weakness Classification | CWE-502 |
| Exploitation Assessment | Exploitation Less Likely |
| Affected Product | Microsoft SharePoint Server Subscription Edition (x64) |
| Security Update (KB) | KB5002945 |
| Fixed Build | 16.0.20326.20278 |
In addition to the scoring metrics, MSRC tracks the operational threat posture of this flaw with the following status indicators:
- Publicly disclosed: No
- Exploited: No
- Customer action required: Yes
Section Summary: CVE-2026-109464 is an Important remote code execution flaw affecting Microsoft SharePoint Server Subscription Edition (x64) with a 8.8 base score, 7.7 temporal score, no active exploitation or prior public disclosure, and mandatory customer patching via KB5002945.
How the Vulnerability Works: CWE-502 and Attack Mechanics
Per Microsoft's official description, Deserialization of untrusted data in Microsoft Office SharePoint allows an authorized attacker to execute code over a network. That root cause maps directly to CWE-502, one of the classic architectural headaches in enterprise web applications.
From general software security principles, serialization is the routine process of converting structured objects into a byte stream or text format so they can travel across a network or sit in storage, while deserialization reconstructs those objects on the receiving end. When an application deserializes incoming data without strictly validating what kind of object is being rebuilt, an attacker can feed it a maliciously structured payload—often called a gadget chain—that tricks the server runtime into executing arbitrary commands as soon as the data is unpacked.
Microsoft's official advisory details clarify two critical operational questions for defenders:
- Attack Vector Mechanics: How could an attacker exploit this vulnerability? An authenticated attacker with low-level access to an affected server could send a specially crafted request to execute code on the server, and user interaction is not required.
- Preview Pane Exposure: Is the Preview Pane an attack vector for this vulnerability? No, the Preview Pane is not an attack vector.
Ruling out the Preview Pane is a welcome detail for desktop and mail security teams, as it confirms this is strictly a server-side request-handling issue rather than a document-viewing trap triggered by unsuspecting end users.
Reading Between the Lines of the CVSS Vector
Why does an 8.8 vulnerability carry an Important label instead of topping the severity chart? Looking closely at the vector string—CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C—explains the balance of risk:
- Network Reachable, Low Complexity (
AV:N/AC:L): The flaw is reachable over a network connection and does not depend on rare race conditions or exotic server configurations to trigger reliably. - Low Privileges Required (
PR:L): An anonymous internet scanner cannot fire off an exploit unauthenticated. However, "low-level access" in an enterprise collaboration environment is rarely a high bar—a single phished domain account, a compromised contractor login, or a shared service credential is enough to clear this hurdle. - Zero User Interaction (
UI:N): The attacker does not need to convince an administrator or colleague to open a poisoned file. Sending the crafted network request directly to the affected server suffices. - Total Tri-Metric Impact (
C:H/I:H/A:H) within Unchanged Scope (S:U): Successful code execution puts confidentiality, integrity, and availability at high risk within the security scope of the server component. - Temporal Modifiers (
E:U/RL:O/RC:C): Unproven exploit maturity (E:U), the availability of an official fix (RL:O), and confirmed report confidence (RC:C) bring the 8.8 base score down to a 7.7 temporal score, aligning with Microsoft's Exploitation Less Likely assessment.
Even with Exploitation Less Likely, seasoned sysadmins know better than to treat authenticated server flaws casually. Intranet collaboration platforms sit at the crossroads of corporate identity and document storage; if an attacker already holds a low-privilege foothold on the network, turning that foothold into server-side code execution is a textbook privilege-escalation and lateral-movement play.
Section Summary: Rooted in CWE-502 untrusted data deserialization, CVE-2026-109464 lets an authenticated user with low-level access send a crafted network request to execute code on the server with zero user interaction and no Preview Pane involvement.
Remediation and Patch Verification Guidance
Because Customer action required: Yes applies to this release, administrators managing on-premises SharePoint infrastructure must schedule maintenance to deploy Microsoft's official fix:
- For Microsoft SharePoint Server Subscription Edition (x64), install KB5002945 to reach fixed build 16.0.20326.20278.
When rolling out SharePoint security updates in production environments, general enterprise administration best practices apply to avoid unexpected farm downtime:
- Stage Before Production: Validate KB5002945 in a non-production or staging environment that mirrors your custom solutions, workflows, and authentication providers before touching production front-end or application servers.
- Complete Configuration Tasks: Remember that installing the SharePoint binary package is typically only half the battle in on-premises farm maintenance; verify through Central Administration and the Products Configuration Wizard (or your standard PowerShell upgrade runbook) that every server in the farm completes database schema and configuration updates cleanly.
- Confirm Target Build Numbers: After maintenance concludes, audit your server inventory and Central Administration patch status pages to confirm that Microsoft SharePoint Server Subscription Edition (x64) reports fixed build 16.0.20326.20278 across every node.
- Tighten Access Hygiene: While scheduling your maintenance window, review account lifecycle policies, audit anomalous authenticated requests against SharePoint web endpoints, and ensure external network exposure is strictly gated behind hardened authentication policies.
For further discussion on scheduling server maintenance windows, handling farm upgrade runbooks, and auditing patch compliance across enterprise environments, check out our ongoing patch management and Windows Server administration discussions right here on WindowsForum.com.
Section Summary: Administrators must deploy KB5002945 to bring Microsoft SharePoint Server Subscription Edition (x64) up to fixed build 16.0.20326.20278, verifying full farm synchronization to neutralize CVE-2026-109464.
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