Microsoft Patches High-Severity Remote Code Execution Vulnerability in SharePoint Server

Microsoft Patches High-Severity SharePoint RCE Vulnerability (CVE-2026-45659)

HIGH
May 26, 2026
5m read
VulnerabilityPatch Management

Related Entities

Organizations

CVE Identifiers

CVE-2026-45659
HIGH
CVSS:8.8

Full Report

Executive Summary

Microsoft has issued security updates for a high-severity remote code execution (RCE) vulnerability, CVE-2026-45659, in Microsoft SharePoint Server. The vulnerability carries a CVSS 3.1 score of 8.8 and affects SharePoint Server Subscription Edition, 2019, and 2016. The flaw can be exploited by an authenticated attacker with minimal permissions (Site Member) to execute arbitrary code on the underlying server. Although Microsoft assesses exploitation as "less likely," the low attack complexity and lack of required user interaction make this a significant risk. All organizations with on-premise SharePoint deployments are urged to apply the necessary patches immediately.


Vulnerability Details

The root cause of CVE-2026-45659 is an insecure deserialization flaw. This class of vulnerability occurs when an application receives serialized data from an untrusted source and deserializes it without proper validation. An attacker can craft a malicious serialized object that, when processed by the SharePoint server, leads to the execution of arbitrary code in the context of the SharePoint application pool service account.

Key characteristics of the vulnerability include:

  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: Low (Authenticated user with Site Member permissions)
  • User Interaction: None
  • Impact: Remote Code Execution

An attacker only needs to gain basic authenticated access to a SharePoint site to exploit this flaw. This makes it particularly dangerous, as credentials for low-privileged accounts are often easier to obtain through phishing or other means.

Affected Systems

The vulnerability impacts the following on-premise Microsoft SharePoint products:

  • Microsoft SharePoint Server Subscription Edition
  • Microsoft SharePoint Server 2019
  • Microsoft SharePoint Enterprise Server 2016

SharePoint Online is not affected by this vulnerability. Patches are available via the standard Microsoft update channels.

Exploitation Status

As of the time of disclosure, Microsoft has stated that it is not aware of any active exploitation in the wild and assesses that exploitation is "less likely." However, SharePoint servers are a perennially popular target for threat actors of all kinds, from nation-state groups to ransomware gangs. Given the low complexity and high impact, it is highly probable that security researchers and malicious actors will develop proof-of-concept (PoC) exploits. Organizations should operate under the assumption that exploitation will become likely in the near future.

Impact Assessment

Successful exploitation of CVE-2026-45659 would grant an attacker the ability to execute code on the SharePoint server. This could lead to a complete compromise of the server, allowing the attacker to:

  • Steal Sensitive Data: Access, modify, or exfiltrate all data stored within the SharePoint environment, including documents, intellectual property, and PII.
  • Lateral Movement: Use the compromised SharePoint server as a beachhead to move laterally within the corporate network.
  • Deploy Ransomware: Install ransomware to encrypt server data and data on connected network shares.
  • Establish Persistent Access: Install backdoors or other malware to maintain long-term access to the network.

Cyber Observables — Hunting Hints

The following patterns may help identify vulnerable or compromised systems:

Type
Log Source
Value
SharePoint ULS Logs
Description
Monitor for unexpected deserialization error messages or exceptions, which could indicate failed exploitation attempts.
Context
Application Logs
Type
Process Name
Value
w3wp.exe
Description
Monitor the SharePoint worker process for suspicious child processes (e.g., cmd.exe, powershell.exe), unusual network connections, or high CPU usage.
Context
EDR / Process Monitoring
Type
Log Source
Value
Windows Event Logs
Description
Look for Event ID 4688 (Process Creation) events originating from the w3wp.exe process that are not part of normal SharePoint operations.
Context
SIEM / Windows Security Logs

Detection Methods

  • Vulnerability Scanning: Use a vulnerability scanner with updated plugins to identify unpatched SharePoint servers in your environment.
  • Version Checks: Manually verify that the latest cumulative updates and security updates have been applied to all SharePoint servers in the farm.
  • Log Analysis: Ingest SharePoint ULS logs and Windows Event Logs into a SIEM. Create rules to alert on suspicious activity originating from the SharePoint worker process (w3wp.exe), such as spawning command shells or making outbound connections to unknown IPs.

For detection, security teams can leverage D3FEND techniques like Process Analysis to monitor the behavior of the SharePoint worker process for anomalies.

Remediation Steps

  1. Patch Immediately: The primary remediation is to apply the security updates released by Microsoft for all affected SharePoint products. Prioritize internet-facing servers.
  2. Verify Installation: After patching, verify that the update was installed successfully and that the build number of the SharePoint farm has been updated.
  3. Principle of Least Privilege: As a compensating control, review user permissions on SharePoint sites. Ensure that users only have the minimum level of access required for their roles. Limit the number of users with Site Member or higher permissions.
  4. Network Segmentation: Restrict administrative access to SharePoint servers to a limited number of management workstations. Do not expose SharePoint management interfaces to the internet.

Applying D3FEND hardening techniques like Software Update is the most effective countermeasure.

Timeline of Events

1
May 26, 2026
This article was published

MITRE ATT&CK Mitigations

The most critical mitigation is to apply the security patches provided by Microsoft to all affected SharePoint servers.

Employing endpoint security solutions that can detect and block common exploit techniques, like those targeting deserialization, can provide an additional layer of defense.

Limiting the number of users with Site Member permissions reduces the attack surface, as an attacker would first need to compromise a privileged account.

D3FEND Defensive Countermeasures

The primary and most effective countermeasure against CVE-2026-45659 is to promptly apply the security updates released by Microsoft. Organizations must have a robust patch management program that can identify all affected SharePoint servers (Subscription Edition, 2019, 2016) within the environment and deploy the necessary updates in a timely manner. Priority should be given to internet-facing servers, as they are the most exposed. After patching, it is crucial to verify that the update was successfully installed across the entire SharePoint farm. Delaying this action leaves the organization vulnerable to remote code execution, which could lead to a full compromise of sensitive corporate data stored in SharePoint.

In addition to patching, security teams should implement process analysis focused on the SharePoint worker process, w3wp.exe. An EDR solution or advanced SIEM logging should be configured to monitor this process for anomalous behavior. Specifically, create alerts for any instance where w3wp.exe spawns suspicious child processes, such as cmd.exe, powershell.exe, cscript.exe, or any other unexpected executable. Successful exploitation of this RCE vulnerability would likely result in such a process tree. By baselining normal SharePoint activity and alerting on these deviations, security teams can create a valuable detection mechanism for exploitation attempts, both for this specific CVE and for future web application vulnerabilities.

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

cve-2026-45659microsoftsharepointrcevulnerabilitypatch managementdeserialization

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.