A critical security flaw in Microsoft SharePoint Server, tracked as CVE-2026-50522, has transitioned from a patched vulnerability to an active threat following the release of a public proof-of-concept (PoC) exploit. Initially addressed in Microsoft's July 2026 Patch Tuesday update, the vulnerability—rated a severe 9.8 CVSS score—is now seeing active exploitation attempts in the wild, as reported by security researchers at watchTowr.
This is not a theoretical risk. The vulnerability allows for unauthenticated remote code execution (RCE) via the deserialization of untrusted data. For organizations running SharePoint, this represents a critical pathway for initial access, ransomware deployment, or lateral movement. Defenders must assume that scanning and exploitation attempts are already underway.
Technical Analysis
Affected Products:
- Microsoft SharePoint Server Subscription Edition
- Microsoft SharePoint Server 2019
- Microsoft SharePoint Server 2016 (if still within extended support)
Vulnerability Details:
- CVE ID: CVE-2026-50522
- CVSS Score: 9.8 (Critical)
- Vulnerability Type: Deserialization of Untrusted Data
- Vector: Network (Adjacent or Network)
Attack Mechanics:
The vulnerability resides in how SharePoint handles specific serialized data objects. An attacker can send a specially crafted HTTP request to a target SharePoint server. When the server attempts to deserialize this payload, it triggers a memory corruption flaw or bypasses security controls, allowing the attacker to execute arbitrary code with the privileges of the SharePoint application pool (typically SYSTEM or a highly privileged service account).
From a defensive perspective, the exploitation typically manifests as the Internet Information Services (IIS) worker process (w3wp.exe) spawning unexpected child processes, such as command shells or PowerShell, to establish persistence or download further payloads.
Exploitation Status:
- Public PoC: Available (watchTowr)
- Active Exploitation: Yes (Confirmed security issues)
- CISA KEV: Expected to be added imminently given the severity and public availability.
Detection & Response
Given the public availability of the exploit code, detection capabilities must be deployed immediately. The following signatures focus on the post-exploitation behavior of the IIS worker process on SharePoint servers.
SIGMA Rules
---
title: Potential SharePoint RCE via w3wp Spawning Shell
id: 8a4b1c99-7d3e-4a5f-9b2d-1e6f3a4c5d6e
status: experimental
description: Detects potential exploitation of CVE-2026-50522 or similar web RCEs by identifying the SharePoint worker process spawning a command shell or PowerShell.
references:
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50522
author: Security Arsenal
date: 2026/07/15
tags:
- attack.initial_access
- attack.execution
- attack.t1190
- attack.t1059.001
logsource:
category: process_creation
product: windows
detection:
selection:
ParentImage|endswith: '\w3wp.exe'
Image|endswith:
- '\cmd.exe'
- '\powershell.exe'
- '\pwsh.exe'
filter_legit:
CommandLine|contains:
- 'AppCmd'
- 'admin'
condition: selection and not filter_legit
falsepositives:
- Legitimate administrative debugging (rare)
level: critical
---
title: SharePoint w3wp Spawning Network Tool
id: 9b5c2d00-8e4f-5b6a-0c3e-2f7a4b5d6e7f
status: experimental
description: Detects the SharePoint worker process spawning network utilities often used for post-exploitation data exfiltration or C2 communication.
references:
- https://attack.mitre.org/techniques/T1071/
author: Security Arsenal
date: 2026/07/15
tags:
- attack.command_and_control
- attack.t1105
logsource:
category: process_creation
product: windows
detection:
selection:
ParentImage|endswith: '\w3wp.exe'
Image|endswith:
- '\certutil.exe'
- '\bitsadmin.exe'
- '\curl.exe'
condition: selection
falsepositives:
- Unknown
level: high
Microsoft Sentinel (KQL)
// Hunt for SharePoint RCE Activity
// Detects w3wp.exe spawning suspicious child processes
DeviceProcessEvents
| where Timestamp > ago(7d)
| where InitiatingProcessFileName =~ "w3wp.exe"
| where FileName in~ ("cmd.exe", "powershell.exe", "pwsh.exe", "certutil.exe", "bitsadmin.exe", "curl.exe")
| project Timestamp, DeviceName, AccountName, InitiatingProcessCommandLine, FileName, ProcessCommandLine, SHA256
| order by Timestamp desc
Velociraptor VQL
-- Hunt for suspicious child processes of SharePoint IIS worker process
SELECT Pid, Name, CommandLine, Exe, Username, StartTime
FROM pslist()
WHERE ParentName =~ "w3wp.exe"
AND Name IN ("cmd.exe", "powershell.exe", "pwsh.exe", "certutil.exe", "curl.exe")
Remediation Script (PowerShell)
# Check SharePoint Build Version for CVE-2026-50522 Exposure
# Note: Replace 'TargetSafeVersion' with the specific version number from the July 2026 Out-of-band or Patch Tuesday update once Microsoft publishes the specific build for your SharePoint version.
$SharePointRoot = "${env:CommonProgramFiles}\Microsoft Shared\Web Server Extensions\16\ISAPI"
$DllPath = Join-Path $SharePointRoot "Microsoft.SharePoint.dll"
if (Test-Path $DllPath) {
$VersionInfo = (Get-Item $DllPath).VersionInfo
Write-Host "Detected SharePoint DLL Version:" $VersionInfo.FileVersion
# Logic to check against patched versions (Placeholder logic)
# Example: If FileVersion is less than the patched version, alert.
$CurrentVersion = [System.Version]$VersionInfo.FileVersion
# UPDATE THIS VALUE with the secure version from the July 2026 advisory
$SecureVersion = [System.Version]"16.0.17000.0"
if ($CurrentVersion -lt $SecureVersion) {
Write-Host "[ALERT] System appears vulnerable to CVE-2026-50522. Please apply the latest July 2026 security update immediately." -ForegroundColor Red
Write-Host "Refer to https://msrc.microsoft.com/update-guide for the exact KB required for your farm version."
} else {
Write-Host "[INFO] System version appears to meet or exceed the security baseline." -ForegroundColor Green
}
} else {
Write-Host "[ERROR] SharePoint DLL not found at expected path. Ensure SharePoint is installed and run as Administrator."
}
Remediation
1. Apply Updates Immediately: The primary remediation for CVE-2026-50522 is patching. Microsoft released fixes in the July 2026 Patch Tuesday update.
- Action: Deploy the latest cumulative updates for your specific version of SharePoint Server immediately.
- Reference: Microsoft Security Update Guide - CVE-2026-50522
2. Inbound Traffic Restriction (Workaround): If patching is delayed, restrict access to SharePoint servers from untrusted networks.
- Action: Utilize network firewalls or Web Application Firewalls (WAF) to block access to the
/pages/or specific application endpoints that handle serialization requests if possible, though blocking all traffic to SharePoint is the only 100% effective workaround until patched. - WAF Signature: Ensure your WAF signatures are updated to detect known deserialization payloads for .NET/IIS.
3. Post-Incident Forensics: If your server was unpatched during the window of active exploitation:
- Review IIS logs (
C:\inetpub\logs\LogFiles) for unusually large POST requests or anomalousUser-Agentstrings. - Check for newly created accounts or scheduled tasks on the SharePoint server.
- Hunt for web shells in the
C:\inetpub\wwwroot\wss\VirtualDirectoriesdirectory structure.
Related Resources
Security Arsenal Penetration Testing Services AlertMonitor Platform Book a SOC Assessment vulnerability-management Intel Hub
Is your security operations ready?
Get a free SOC assessment or see how AlertMonitor cuts through alert noise with automated triage.