Back to Intelligence

CVE-2026-55040: Unauthenticated SharePoint RCE Found by AI Agent — Detection, Hunting, and Patching Guide

SA
Security Arsenal Team
August 11, 2026
11 min read

Security researchers have disclosed a critical vulnerability chain in Microsoft SharePoint Server — tracked as CVE-2026-55040 (CVSS 9.1) — that allows a remote attacker with no credentials whatsoever to authenticate as any user, including a farm administrator, and achieve unauthenticated remote code execution. A significant portion of the vulnerability research itself was performed by an AI agent, which is a milestone the offensive community has been predicting for years: machine-speed vulnerability discovery is no longer theoretical.

The affected products are SharePoint Server Subscription Edition, SharePoint Server 2019, and SharePoint Server 2016 — in other words, effectively every on-premises SharePoint deployment currently supported by Microsoft. SharePoint Online (Microsoft 365) is not the target here; this is squarely an on-premises and IaaS-hosted problem, and it lands hardest on the organizations that internet-expose SharePoint for extranet collaboration or hybrid integration.

If you run on-prem SharePoint and it is reachable from the internet — or from a broad internal user population — treat this as a patch-now event. The combination of unauthenticated, any-user impersonation including administrators, and code execution is the exact profile that ransomware operators and initial access brokers prioritize within hours of disclosure. We saw this playbook executed at scale with the 2025 SharePoint auth-bypass exploitation waves; defenders who waited for "confirmation of exploitation" then were conducting IR engagements within the week. Do not repeat that mistake in 2026.


Technical Analysis

What the flaw chain does

Based on the researcher disclosure, the vulnerability chain breaks into two logical stages:

  1. Authentication bypass / arbitrary user impersonation. The attacker can cause the SharePoint server to treat their request as originating from any user account — including site collection administrators and farm administrators — without presenting valid credentials. This class of flaw in SharePoint historically lives in how the server handles crafted requests against authentication-adjacent endpoints or how it processes forged identity tokens/headers during request deserialization.
  2. Privilege-to-code-execution escalation. Authenticated-as-admin access in SharePoint is functionally equivalent to code execution: farm administrators can deploy solutions, execute server-side operations, and interact with components that run as the SharePoint service account (typically a highly privileged account with database and often local SYSTEM-adjacent rights).

The net effect: a single unauthenticated network position becomes code execution on the SharePoint host, with a trusted process (w3wp.exe running the SharePoint application pool) as the launch point and a privileged service account as the execution context.

Affected products

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

The AI-assisted research angle — why it matters to defenders

The researchers stated that a significant part of the discovery work was performed by an AI agent. Strip away the novelty and focus on the operational implication: the cost and time of chaining multi-step vulnerabilities in complex, legacy codebases like SharePoint just dropped by an order of magnitude. SharePoint has a massive attack surface, a long history of deserialization and auth-bypass flaws, and an enormous on-prem install base. If AI-assisted research produced one unauthenticated 9.1 chain, assume more are in the pipeline — from researchers and from adversaries running the same tooling. Your defensive posture cannot assume vulnerability scarcity anymore. Patch cadence and detection depth now carry the entire load.

Exploitation status

At time of disclosure, the flaw has been publicly described by researchers and addressed by Microsoft. Regardless of whether in-the-wild exploitation is confirmed on day one, treat public technical disclosure of an unauthenticated SharePoint RCE as imminent exploitation. The 2025 SharePoint exploitation campaigns demonstrated that working exploit code follows detailed write-ups within days, and internet-wide scanning for vulnerable SharePoint follows within hours. Check Microsoft's advisory and CISA's Known Exploited Vulnerabilities catalog daily until your farm is patched — if CVE-2026-55040 lands on KEV, federal remediation deadlines will apply and private-sector organizations should adopt the same timeline.


Detection & Response

Post-exploitation behavior on SharePoint is highly consistent regardless of which CVE opened the door. Attackers who achieve code execution via SharePoint almost universally do one of three things: drop a web shell into a web-accessible SharePoint directory, spawn command interpreters from the IIS worker process, or enumerate and steal the SharePoint configuration/content databases. The detections below target those behaviors and will catch exploitation of CVE-2026-55040 as well as the next SharePoint auth bypass that surfaces.

Sigma Rules

YAML
---
title: IIS SharePoint Worker Process Spawning Command Interpreter
id: 3c8f4a21-7b2e-4d91-a6f3-9e1c5b8d2a47
status: experimental
description: Detects w3wp.exe (IIS worker process hosting SharePoint) spawning cmd.exe, powershell.exe, or other LOLBins. Strong indicator of post-exploitation following SharePoint RCE such as CVE-2026-55040.
references:
  - https://thehackernews.com/2026/08/researchers-disclose-ai-assisted.html
  - https://attack.mitre.org/techniques/T1190/
  - https://attack.mitre.org/techniques/T1059/
author: Security Arsenal
date: 2026/08/14
tags:
  - attack.initial_access
  - attack.t1190
  - attack.execution
  - attack.t1059
logsource:
  category: process_creation
  product: windows
detection:
  selection_parent:
    ParentImage|endswith: '\w3wp.exe'
  selection_child:
    Image|endswith:
      - '\cmd.exe'
      - '\powershell.exe'
      - '\pwsh.exe'
      - '\cscript.exe'
      - '\wscript.exe'
      - '\mshta.exe'
      - '\rundll32.exe'
      - '\regsvr32.exe'
      - '\certutil.exe'
      - '\bitsadmin.exe'
      - '\whoami.exe'
      - '\nltest.exe'
      - '\net.exe'
      - '\net1.exe'
  condition: selection_parent and selection_child
falsepositives:
  - Rare SharePoint timer jobs or custom solutions invoking scripts; baseline per farm and filter known-good command lines
level: high
---
title: Web Shell or ASPX File Written to SharePoint LAYOUTS Directory
id: 8d1e6b92-4c3f-4a85-b9d2-2f7a4e6c9b51
status: experimental
description: Detects creation or modification of .aspx/.ashx/.asmx files in SharePoint TEMPLATE\LAYOUTS or other web-served hive directories, consistent with web shell deployment after exploitation of CVE-2026-55040.
references:
  - https://thehackernews.com/2026/08/researchers-disclose-ai-assisted.html
  - https://attack.mitre.org/techniques/T1505/003/
author: Security Arsenal
date: 2026/08/14
tags:
  - attack.persistence
  - attack.t1505.003
  - attack.initial_access
  - attack.t1190
logsource:
  category: file_event
  product: windows
detection:
  selection_path:
    TargetFilename|contains:
      - '\Web Server Extensions\16\TEMPLATE\LAYOUTS\'
      - '\Web Server Extensions\15\TEMPLATE\LAYOUTS\'
      - '\Web Server Extensions\14\TEMPLATE\LAYOUTS\'
      - '\Web Server Extensions\16\TEMPLATE\CONTROLTEMPLATES\'
      - '\Web Server Extensions\16\TEMPLATE\ADMIN\'
  selection_ext:
    TargetFilename|endswith:
      - '.aspx'
      - '.ashx'
      - '.asmx'
      - '.asp'
  condition: selection_path and selection_ext
falsepositives:
  - SharePoint solution (WSP) deployments and cumulative updates write legitimately; correlate with patch windows and change tickets
level: high
---
title: Suspicious Outbound Connection from SharePoint IIS Worker Process
id: 5b2c9d74-1e6a-4f38-a7c1-6d4b8e2f3a96
status: experimental
description: Detects w3wp.exe hosting SharePoint initiating outbound connections to rare external IPs, consistent with C2 or data exfiltration following SharePoint compromise via CVE-2026-55040.
references:
  - https://thehackernews.com/2026/08/researchers-disclose-ai-assisted.html
  - https://attack.mitre.org/techniques/T1071/001/
author: Security Arsenal
date: 2026/08/14
tags:
  - attack.command_and_control
  - attack.t1071.001
  - attack.exfiltration
logsource:
  category: network_connection
  product: windows
detection:
  selection:
    Image|endswith: '\w3wp.exe'
    Initiated: 'true'
  filter_microsoft:
    DestinationHostname|endswith:
      - '.microsoft.com'
      - '.microsoftonline.com'
      - '.sharepoint.com'
      - '.windows.net'
      - '.office.com'
  filter_internal:
    DestinationIp|startswith:
      - '10.'
      - '172.16.'
      - '192.168.'
  condition: selection and not 1 of filter_*
falsepositives:
  - Hybrid SharePoint federation, search federation, and vendor integration calls; whitelist known SaaS endpoints per farm
level: medium

KQL — Microsoft Sentinel / Defender XDR

Hunt for the full kill chain: IIS worker spawning interpreters, web-shell file drops, and abnormal authentication patterns against SharePoint hosts. Run these across at least the last 30 days — if you were exposed pre-disclosure, assume pre-patch probing occurred.

KQL — Microsoft Sentinel / Defender
// Stage 1: SharePoint IIS worker process spawning command interpreters or recon tools
let SharePointServers = dynamic(["w3wp.exe"]);
DeviceProcessEvents
| where TimeGenerated > ago(30d)
| where InitiatingProcessFileName =~ "w3wp.exe"
| where FileName in~ ("cmd.exe","powershell.exe","pwsh.exe","whoami.exe","net.exe","nltest.exe","ipconfig.exe","systeminfo.exe","certutil.exe","bitsadmin.exe","mshta.exe","rundll32.exe")
| project TimeGenerated, DeviceName, AccountName, FileName, ProcessCommandLine, InitiatingProcessCommandLine, SHA256
| order by TimeGenerated desc;

// Stage 2: Web shell artifacts written into SharePoint hive directories
DeviceFileEvents
| where TimeGenerated > ago(30d)
| where FolderPath has_any ("Web Server Extensions\\16\\TEMPLATE\\LAYOUTS","Web Server Extensions\\15\\TEMPLATE\\LAYOUTS","CONTROLTEMPLATES")
| where FileName endswith_cs ".aspx" or FileName endswith_cs ".ashx" or FileName endswith_cs ".asmx"
| project TimeGenerated, DeviceName, FolderPath, FileName, InitiatingProcessFileName, InitiatingProcessAccountName, SHA256
| order by TimeGenerated desc;

// Stage 3: Unauthenticated-then-admin anomalies — spikes in 401s followed by successful admin actions in IIS logs (via W3CIISLog or CommonSecurityLog ingestion)
CommonSecurityLog
| where TimeGenerated > ago(7d)
| where DeviceProduct has "IIS" or ApplicationProtocol == "http"
| where DestinationHostName has_any ("sharepoint","sp") or DeviceAddress in (dynamic([])) // scope to your SharePoint IPs
| summarize TotalRequests=count(), AuthFailures=countif(AdditionalExtensions has "401"), SuccessAfterFail=countif(AdditionalExtensions has "200") by SourceIP, bin(TimeGenerated, 1h)
| where AuthFailures > 50 and SuccessAfterFail > 0
| order by AuthFailures desc;

Velociraptor VQL — Endpoint Hunt

Use this artifact across all SharePoint front-end and application servers to surface both live child processes of the IIS worker and recently written executable web content in the SharePoint hive.

VQL — Velociraptor
-- Hunt: SharePoint post-exploitation indicators (CVE-2026-55040)
-- Part 1: w3wp.exe with suspicious child processes
SELECT Pid, Ppid, Name, Exe, CommandLine, Username, CreateTime
FROM pslist()
WHERE Name =~ '(?i)cmd|powershell|pwsh|certutil|mshta|rundll32|whoami|net\.exe'
  AND Ppid IN (
      SELECT Pid FROM pslist() WHERE Name =~ '(?i)w3wp'
  )

-- Part 2: Recently modified script-executable files in SharePoint LAYOUTS directories
SELECT FullPath, Size, Mtime, Atime
FROM glob(globs=[
  'C:/Program Files/Common Files/microsoft shared/Web Server Extensions/16/TEMPLATE/LAYOUTS/**/*.aspx',
  'C:/Program Files/Common Files/microsoft shared/Web Server Extensions/16/TEMPLATE/LAYOUTS/**/*.ashx',
  'C:/Program Files/Common Files/microsoft shared/Web Server Extensions/15/TEMPLATE/LAYOUTS/**/*.aspx',
  'C:/Program Files/Common Files/microsoft shared/Web Server Extensions/14/TEMPLATE/LAYOUTS/**/*.aspx'
])
WHERE Mtime > now() - 60*24*3600
ORDER BY Mtime DESC

Verification & Hardening Script

Run this on every SharePoint server to inventory patch state, check for web-shell artifacts, and confirm defensive controls (AMSI integration for SharePoint is a high-value control against in-memory attacks on the request pipeline).

PowerShell
# CVE-2026-55040 verification and hardening sweep - run elevated on each SharePoint server

# 1. Report SharePoint build and installed updates (compare against Microsoft advisory build floor)
Get-ItemProperty HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* |
  Where-Object { $_.DisplayName -match 'SharePoint' } |
  Select-Object DisplayName, DisplayVersion, InstallDate | Format-Table -AutoSize

$spBuild = (Get-Item "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\ISAPI\Microsoft.SharePoint.dll" -ErrorAction SilentlyContinue).VersionInfo.ProductVersion
Write-Output "SharePoint product build: $spBuild  <-- VERIFY against the fixed build listed in the MSRC advisory for CVE-2026-55040"

# 2. Sweep LAYOUTS/CONTROLTEMPLATES for script files modified in the last 60 days (potential web shells)
$hiveRoots = @('15','16') | ForEach-Object { "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\$_\TEMPLATE" }
foreach ($root in $hiveRoots) {
  Get-ChildItem -Path $root -Recurse -Include *.aspx,*.ashx,*.asmx -ErrorAction SilentlyContinue |
    Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-60) } |
    Select-Object FullName, LastWriteTime, Length | Format-Table -AutoSize
}

# 3. Confirm AMSI is loaded and Defender real-time protection is active on the SharePoint servers
Get-MpComputerStatus | Select-Object AMServiceEnabled, AntivirusEnabled, RealTimeProtectionEnabled, AMRunningMode | Format-List

# 4. Audit recent process lineage: w3wp spawning interpreters (last 7 days, requires process auditing or Defender events)
Get-WinEvent -FilterHashtable @{LogName='Security'; Id=4688; StartTime=(Get-Date).AddDays(-7)} -ErrorAction SilentlyContinue |
  Where-Object { $_.Message -match 'w3wp.exe' -and $_.Message -match 'cmd.exe|powershell.exe|certutil.exe|mshta.exe' } |
  Select-Object TimeCreated, Message -First 50 | Format-List

# 5. Restrict outbound egress from SharePoint servers as interim mitigation (allow only required destinations)
# Implement via perimeter firewall policy: deny all outbound from SharePoint hosts except Microsoft update/CRL endpoints and approved SaaS
Write-Output "ACTION: Confirm perimeter egress rules restrict SharePoint servers to approved destinations only."

Remediation

  1. Apply Microsoft's security update for CVE-2026-55040 immediately on all SharePoint Server Subscription Edition, 2019, and 2016 farms. Pull the exact KB and minimum fixed build from the official Microsoft Security Response Center advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55040 — verify your build number against the fixed build listed there, not against a date assumption. Patch application servers and all front-ends; do not leave a single unpatched node in the farm.
  2. Take internet-facing SharePoint offline or behind a restrictive ACL/VPN until patched. There is no configuration workaround that neutralizes an unauthenticated impersonation chain of this class. If the farm cannot be patched inside 24 hours, unauthenticated network reachability is the variable you control.
  3. Monitor CISA KEV (https://www.cisa.gov/known-exploited-vulnerabilities-catalog) — if CVE-2026-55040 is added, BOD 22-01 deadlines apply to federal agencies and every private organization should adopt the same clock.
  4. Rotate credentials after patching if the farm was exposed pre-patch: SharePoint service accounts, farm admin accounts, the farm passphrase, and any application pool identities. Unauthenticated code execution means credential material in memory or config should be considered compromised.
  5. Hunt before you declare clean. Run the KQL and VQL above over the 30+ days preceding patch date. Look specifically for .aspx drops in the hive, w3wp.exe child processes, and unfamiliar service-account logons. Exploitation that occurred before patching survives patching.
  6. Enable and verify AMSI integration for SharePoint and ensure Microsoft Defender (or equivalent EDR with tamper protection) is running on every farm server. AMSI inspection of SharePoint requests materially raises the cost of in-memory exploitation.
  7. Segment and restrict egress. SharePoint servers should not be able to initiate arbitrary outbound connections. Egress filtering converts a successful RCE into a contained, detectable event.
  8. Assume AI-accelerated vulnerability discovery is the new baseline. Compress your SharePoint patch SLA to days, not maintenance-window cycles. Organizations that treated the 2025 SharePoint campaigns as a one-off were structurally unprepared for this disclosure — fix the process, not just this CVE.

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.