While cloud-hosted services handle backend patching behind the scenes, administrators managing on-premises collaboration farms have work to do. If you run Microsoft SharePoint Server Subscription Edition (x64), here is the complete technical breakdown, risk profile, and exact remediation path you need to secure your environment.
Vulnerability Overview and Official MSRC Telemetry
According to Microsoft's official advisory data, CVE-2026-124223 stems from improper handling of serialized objects—classified under CWE-502 (Deserialization of Untrusted Data). Specifically, Microsoft's description notes: Deserialization of untrusted data in Microsoft Office SharePoint allows an authorized attacker to execute code over a network.
To put all the core metrics in one place for your patch management review, here is the official MSRC scorecard for this release:
| Metric / Field | Official Value |
|---|---|
| CVE Identifier | CVE-2026-124223 |
| Vulnerability Title | Microsoft Office SharePoint Remote Code Execution Vulnerability |
| Severity Rating | Important |
| CVSS v3.1 Base Score | 8.8 |
| CVSS v3.1 Temporal Score | 7.7 |
| CVSS 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 |
| 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 |
Official Status Indicators
- Publicly disclosed: No
- Exploited: No
- Customer action required: Yes
Summary: CVE-2026-124223 is a network-accessible remote code execution flaw in Microsoft SharePoint Server Subscription Edition (x64) that has neither been publicly disclosed prior to patching nor exploited in the wild, though administrative patching is required.
How the Attack Works: APIs and Unsafe Deserialization
Why do deserialization bugs consistently give security engineers heartburn? From general application security principles, serialization is the process of converting complex software objects into a stream of bytes or structured text so they can be transmitted across a network or stored in memory. Deserialization reverses that process. When an application deserializes untrusted or unsafe data without strict type validation, an attacker can pass a maliciously structured payload that tricks the server into instantiating unintended objects and executing arbitrary code as the payload unpacks.
In its official advisory guidance addressing how an attacker could exploit CVE-2026-124223, MSRC explains that an adversary can target vulnerable APIs via a deserialization of unsafe data input flaw. Specifically, exploitation requires a user to access a susceptible API on an affected version of SharePoint using specially-formatted input, which can result in remote code execution directly on the SharePoint Server.
Breaking down the official CVSS v3.1 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) clarifies both why the base score reaches 8.8 and why Microsoft assigns an Important rating rather than Critical:
- Attack Vector — Network (
AV:N) & Attack Complexity — Low (AC:L): The susceptible API is reachable over the network, and exploiting it does not depend on rare race conditions or convoluted server configurations once an attacker has access. - Privileges Required — Low (
PR:L): This is the key gatekeeper. An unauthenticated anonymous internet user cannot simply fire a payload at a locked-down login screen. The attacker must already possess valid, basic user credentials ("an authorized attacker") capable of reaching the susceptible SharePoint API. - User Interaction — None (
UI:N): No administrator or fellow user needs to click a link or open a poisoned document for the attack to succeed. - Scope — Unchanged (
S:U) & High Impact (C:H/I:H/A:H): Successful code execution compromises confidentiality, integrity, and availability completely within the context of the affected SharePoint Server component. - Temporal Factors (
E:U/RL:O/RC:C): Because exploit maturity is unproven (E:U), an official remediation level is available (RL:O), and report confidence is confirmed (RC:C), the temporal score steps down from 8.8 to 7.7.
Even with Microsoft's assessment of Exploitation Less Likely, low-privilege authentication is a remarkably thin barrier inside large organizations. How hard is it for a threat actor to phish a single contractor account, compromise one domain workstation, or leverage an insider account? Once inside the perimeter with standard user permissions, an unpatched SharePoint server becomes an inviting pivot point housing wide swaths of enterprise documentation.
Summary: While authentication is required (PR:L), any authorized user able to reach a susceptible SharePoint API with specially-formatted input could trigger remote code execution without any additional user interaction.
Patch Guidance and Operational Considerations
Because Customer action required: Yes applies to on-premises deployments, administrators running affected farms must schedule maintenance to apply Microsoft's official update.
- Official Remediation: For Microsoft SharePoint Server Subscription Edition (x64), install KB5002945 to reach fixed build 16.0.20326.20278.
Practical Deployment Tips for SharePoint Administrators
Synthesizing standard Windows Server and SharePoint administration best practices, keep the following operational checks in mind when rolling out KB5002945:
- Stage Before Production: SharePoint farms often rely on custom web parts, workflows, or third-party API integrations. Validate KB5002945 in a staging farm first to ensure tighter deserialization checks do not disrupt legacy custom integrations that interact with SharePoint APIs.
- Don't Forget the Configuration Wizard: Downloading and installing the binary package onto the host OS is only half the SharePoint patching dance. Ensure your maintenance window accounts for running the SharePoint Products Configuration Wizard (or the equivalent PowerShell upgrade cmdlets) across farm nodes so database schemas and service binaries fully advance to fixed build 16.0.20326.20278.
- Verify Your Build Number: After patching completes, confirm in SharePoint Central Administration that the farm build version reflects 16.0.20326.20278 across every server role in the topology.
- Audit API Exposure: While preparing for your maintenance window, ensure your SharePoint farm is not unnecessarily exposed directly to the public internet without strong pre-authentication boundaries, and monitor authentication logs for anomalous API requests from standard user accounts.
For ongoing discussion on enterprise patch management, Windows Server maintenance windows, and Microsoft security advisories, check out our dedicated security and server administration boards right here on WindowsForum.com.
Summary: Administrators running Microsoft SharePoint Server Subscription Edition (x64) should deploy KB5002945 and complete farm configuration upgrades to verify their servers reach fixed build 16.0.20326.20278.
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