Microsoft SharePoint remote code execution through unsafe deserialization

Note: This data is for reference and cybersecurity research purposes only.CyStack advises users not to use this information for unlawful purposes.

What is CVE-2026-58644?

CVE-2026-58644 is a vulnerability classified as Deserialization of Untrusted Data, affecting Microsoft SharePoint Enterprise Server 2016 (affected versions: 16.0.0 – < 16.0.5556.1005), Microsoft SharePoint Server 2019 (affected versions: 16.0.0 – < 16.0.10417.20153), and Microsoft SharePoint Server Subscription Edition (affected versions: 16.0.0 – < 16.0.19725.20384). This vulnerability is rated Critical, with a CVSS score of 9.8. This vulnerability has been observed being exploited in the wild.

Overview

Original source data

Deserialization of untrusted data in Microsoft Office SharePoint allows an unauthorized attacker to execute code over a network.

Affected products and scope

The affected and fixed boundaries supported by the CNA and Microsoft advisory data are:

  • Microsoft SharePoint Enterprise Server 2016: affected from 16.0.0 through versions less than 16.0.5556.1005; fixed in 16.0.5556.1005.
  • Microsoft SharePoint Server 2019: affected from 16.0.0 through versions less than 16.0.10417.20153; fixed in 16.0.10417.20153.
  • Microsoft SharePoint Server Subscription Edition: affected from 16.0.0 through versions less than 16.0.19725.20384; fixed in 16.0.19725.20384.

Products or release branches not listed here are not established as either safe or affected by the available evidence.

Technical details

The weakness is CWE-502, involving Microsoft SharePoint processing data that has been deserialized without sufficient trust. The record identifies remote code execution as the outcome, but does not disclose the serialized object type, endpoint, parser, or specific code path involved. The normalized record describes network reachability, low attack complexity, no user interaction, and no required privileges, while a Microsoft advisory FAQ describes a network attacker authenticated as at least a Site Owner who could write and execute code remotely. These descriptions are not fully consistent, so the exact authentication requirement remains unresolved and should be validated against the deployment. The supported affected scope is limited to the SharePoint Server branches listed in affected_summary.

Exploitability

  • Reachability: The vulnerability is network-reachable, and the Microsoft advisory states that the attack can be performed from the Internet.
  • Authentication and interaction: The normalized record describes no required privileges and no user interaction. However, Microsoft's FAQ describes an attacker authenticated as at least a Site Owner, so the precise access precondition is not fully resolved.
  • Complexity: The record describes low attack complexity.
  • Exploitation status: The Microsoft advisory data reports exploitation detected, and CISA records the vulnerability as exploited. Public exploit status is inconsistent: the supplied record marks a public exploit, while the Microsoft advisory data states Publicly Disclosed:No; public exploit availability should therefore be treated as unconfirmed.
  • No specific campaign, victim, payload, or compromise indicator is confirmed in the sources reviewed.

Technical impact

The vulnerability can lead to remote code execution on a SharePoint server through untrusted deserialized data. Possible technical outcomes include reading or modifying data, changing configuration, and disrupting service, but the actual extent depends on the SharePoint process account, farm configuration, and connections to other systems. The normalized record describes high confidentiality, integrity, and availability consequences, but does not identify the exact execution account or establish lateral movement into other systems. The authentication condition is also inconsistent between the normalized vector and Microsoft's FAQ, so deployments should not be assumed to share identical exploitation requirements.

Business impact

Successful exploitation could allow code execution in the SharePoint server context, potentially affecting the confidentiality, integrity, and availability of the service. Depending on the service account, farm permissions, and stored data, consequences could include access to SharePoint content, unauthorized changes to content or configuration, and service disruption. If the server can reach internal systems, code execution could increase the risk of further compromise within the permissions available to that server. The record does not establish a specific breach, data loss event, or campaign, so these consequences should be treated as possible outcomes rather than confirmed events.

Remediation

  1. Install Microsoft's security updates for each affected branch:
  • Microsoft SharePoint Enterprise Server 2016: update to 16.0.5556.1005, corresponding to KB 5002880.
  • Microsoft SharePoint Server 2019: update to 16.0.10417.20153, corresponding to KB 5002874.
  • Microsoft SharePoint Server Subscription Edition: update to 16.0.19725.20384, corresponding to KB 5002873.
  1. Verify the resulting build on every server and every farm node. Updating one server or one release branch does not establish coverage for other deployment branches.
  2. If immediate updating is not possible, apply Microsoft's mitigation guidance and assess Internet exposure for each asset. CISA requires risk-prioritized update and forensics-triage measures; if mitigations are unavailable, consider discontinuing use of the product.
  3. Because advisory data reports exploitation, perform incident response and forensic review for potentially exposed servers before or alongside remediation. Applying the update does not by itself prove that a server was not previously compromised.

Detection

  1. Inventory every farm and server running Microsoft SharePoint Enterprise Server 2016, Microsoft SharePoint Server 2019, or Microsoft SharePoint Server Subscription Edition.
  2. Check the installed build on each server and compare it with the affected boundaries and fixed builds in affected_summary. Check every farm node, not only the server receiving direct traffic.
  3. Identify SharePoint servers reachable from the Internet or other untrusted networks, and document the authentication requirements for those paths.
  4. Review SharePoint and operating system telemetry for unusual remote code execution, unauthorized content or configuration changes, service changes, and suspicious outbound connections. These are precautionary monitoring checks, not Microsoft-confirmed indicators.
  5. The reviewed advisory does not provide specific log events or IOCs. The absence of suspicious events does not prove that a server is safe, especially because exploitation has been reported.
Sources (15)
Learn more

Run an in-depth assessment with complete web risk management

CyStack VulnScan continuously discovers assets, validates vulnerabilities, and helps security teams prioritize remediation across the organization.