Microsoft SharePoint Weak Authentication Exploitation (CVE-2026-55040)
Detects exploitation of CVE-2026-55040, a weak authentication vulnerability (CWE-1390) in Microsoft SharePoint that allows attackers to bypass or abuse insufficient authentication controls to gain unauthorized access to SharePoint content and administrative surfaces. This CVE is listed in the CISA KEV catalog with active in-the-wild exploitation observed as of August 2026. Detection focuses on anomalous authentication patterns against SharePoint (_layouts, _api, _vti_bin endpoints), unauthenticated or under-authenticated access to protected resources, suspicious ToolPane/ViewState activity, and post-exploitation web shell or process spawning from the SharePoint w3wp.exe worker process.
Vulnerability Intelligence
KEV — Known ExploitedAffected Software
- Vendor
- Microsoft
- Product
- SharePoint
Weakness (CWE)
Timeline
- Disclosed
- August 18, 2026
References & Proof of Concept
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55040
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://nvd.nist.gov/vuln/detail/CVE-2026-55040
- https://thehackernews.com/2026/08/attackers-exploit-sharepoint.html
- https://thehackernews.com/2026/08/researchers-disclose-ai-assisted.html
CVSS
What is CVE-2026-55040 Microsoft SharePoint Weak Authentication Exploitation (CVE-2026-55040)?
Microsoft SharePoint Weak Authentication Exploitation (CVE-2026-55040) (CVE-2026-55040) maps to the Initial Access and Privilege Escalation and Credential Access tactics — the adversary is trying to get into your network in MITRE ATT&CK.
This page provides production-ready detection logic for Microsoft SharePoint Weak Authentication Exploitation (CVE-2026-55040), covering the data sources and telemetry it touches: Microsoft Sentinel, IIS Logs, W3CIISLog. The queries below are rated high severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.
MITRE ATT&CK
let sharepointHosts = dynamic([]);
let suspiciousPaths = dynamic(["/_layouts/15/ToolPane.aspx", "/_api/web", "/_vti_bin", "/_layouts/15/spinstalladmincomponent.aspx", "/_layouts/signout.aspx"]);
W3CIISLog
| where csUriStem has_any (suspiciousPaths) or csUriStem has "/_layouts/" or csUriStem has "/_api/"
| extend AuthHeader = tostring(column_ifexists("csAuthorization", ""))
| where (scStatus in (200, 302) and (csMethod == "POST")) and (isempty(csUsername) or csUsername == "-")
| project TimeGenerated, sSiteName, sComputerName, cIP, csMethod, csUriStem, csUriQuery, scStatus, csUserAgent, csUsername, csReferer
| summarize RequestCount = count(), Paths = make_set(csUriStem, 20), UserAgents = make_set(csUserAgent, 10), FirstSeen = min(TimeGenerated), LastSeen = max(TimeGenerated) by cIP, sComputerName
| where RequestCount > 3
| order by RequestCount desc Identifies unauthenticated (empty or '-' username) POST requests to sensitive SharePoint _layouts/_api/_vti_bin endpoints returning 200/302, indicating authentication bypass consistent with CVE-2026-55040 exploitation.
Data Sources
Required Tables
False Positives
- Legitimate anonymous access configured on public-facing SharePoint sites for specific document libraries.
- Load balancer or uptime monitoring health checks hitting SharePoint endpoints without credentials.
- Search crawler service accounts that authenticate via a mechanism not captured in the csUsername field.
Sigma rule & cross-platform mapping
The detection logic for Microsoft SharePoint Weak Authentication Exploitation (CVE-2026-55040) (CVE-2026-55040) above is provided in a vendor-neutral
form so you can deploy it on any SIEM. The same logic is shipped here as native
KQL (Microsoft Sentinel / Defender), SPL (Splunk), Elastic (Elastic Security (EQL)), QRadar (IBM QRadar (AQL)), Sumo (Sumo Logic CSE), YARA-L (Google Chronicle / SecOps), LogScale (CrowdStrike LogScale (CQL)) queries. In Sigma terms, this detection targets the
following logsource:
logsource:
product: windows Browse the community-maintained Sigma rules for this technique:
Platform-specific guides for CVE-2026-55040
References (6)
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-55040
- https://nvd.nist.gov/vuln/detail/CVE-2026-55040
- https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk
- https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk
- https://thehackernews.com/2026/08/attackers-exploit-sharepoint.html
- https://thehackernews.com/2026/08/researchers-disclose-ai-assisted.html
Testing Methodology
Validate this detection against 3 adversary techniques from Atomic Red Team. Each test below lists the behaviour to exercise and the telemetry you should expect to see. Executable commands and cleanup steps are available with Pro.
- Test 1Simulate unauthenticated POST to SharePoint ToolPane endpoint
Expected signal: IIS W3C log entry showing a POST to /_layouts/15/ToolPane.aspx with an empty/'-' username and a 200/302 status code.
- Test 2Simulate unauthenticated SharePoint _api access burst
Expected signal: Five IIS log entries for POST /_api/web/lists with no authenticated username.
- Test 3Simulate w3wp.exe spawning suspicious child process
Expected signal: Process-creation event (Sysmon EID 1 / EDR ProcessRollup) showing cmd.exe with a parent of w3wp.exe (when run under the SharePoint app pool context).
Response Playbook
Triage
- Confirm the affected host is running Microsoft SharePoint and identify its patch level against the MSRC advisory for CVE-2026-55040; determine whether the applicable security update is installed.
- Review the source IPs from the detection: enrich against threat intelligence and determine whether they are internal, VPN, or external/untrusted, and whether they appear in the CISA KEV-linked exploitation reporting.
- Examine the IIS logs for the flagged host to confirm unauthenticated POSTs to /_layouts/, /_api/, or /_vti_bin/ returned 200/302, and correlate with any subsequent w3wp.exe child-process activity or new .aspx files under the SharePoint LAYOUTS/wwwroot directories.
- Check for indicators of web shell deployment (new/modified .aspx, .ashx, .asmx files) and unexpected changes to SharePoint machine keys or ViewState configuration.
Containment
- Isolate the affected SharePoint server from the network if web shell or hands-on-keyboard activity is confirmed, preserving volatile state for forensics.
- Apply the Microsoft security update for CVE-2026-55040 immediately per CISA BOD 26-04 prioritization; if patching is not immediately possible, restrict inbound access to SharePoint _layouts/_api/_vti_bin endpoints at the WAF/reverse proxy.
- Rotate SharePoint ASP.NET machine keys and invalidate existing sessions to defeat forged/replayed authentication material.
- Reset credentials for any service and administrative accounts that may have been exposed through the weak-authentication bypass.
Evidence Collection
- Preserve full IIS W3C logs, SharePoint ULS logs, and Windows Security/Sysmon event logs from the affected host for the exploitation window.
- Capture a forensic image or at minimum the SharePoint wwwroot and LAYOUTS directories to retain any dropped web shells and timestamps.
- Export the process-creation telemetry showing w3wp.exe child processes and their full command lines.
- Collect the SharePoint web.config and machine key configuration as evidence of pre/post exploitation state.
Escalation Criteria
- ! Escalate to incident response and management if a web shell, unauthorized administrative account, or interactive command execution under the SharePoint app pool is confirmed.
- ! Escalate if lateral movement, credential dumping, or data exfiltration from SharePoint content databases is observed following the initial access.
- ! Notify the CISA-required reporting chain given this CVE is in the KEV catalog and subject to BOD 26-04 remediation timelines.
- ! Escalate if the affected server is internet-facing and exploitation success (200/302 to sensitive endpoints without auth) is confirmed.
Investigation Guide
Forensic Artifacts
- >
IIS W3C logs showing unauthenticated POSTs to /_layouts/, /_api/, or /_vti_bin/ with 200/302 responses. - >
New or modified .aspx/.ashx/.asmx files under the SharePoint LAYOUTS or wwwroot directories. - >
SharePoint ULS logs and Windows event logs showing anomalous authentication or process creation from w3wp.exe. - >
Modified machine keys or ViewState/web.config settings in the SharePoint site configuration.
Tuning Guidance
Baseline which SharePoint sites in your environment legitimately allow anonymous access and exclude those specific site collections/paths from the unauthenticated-POST logic. Confirm your IIS logging captures the cs-username field reliably (some reverse-proxy or NTLM configurations may leave it blank for legitimate authenticated traffic); if so, pivot the detection toward the w3wp.exe child-process and web-shell file-creation signals, which have far lower false-positive rates. Tune the request-count threshold to your traffic volume.
Hunting Queries
Hunts for repeated unauthenticated POSTs to the highest-signal SharePoint exploitation endpoints across IIS logs.
W3CIISLog | where csUriStem has_any ("/_layouts/15/ToolPane.aspx", "/_vti_bin/", "/_api/web") | where csMethod == "POST" | where isempty(csUsername) or csUsername == "-" | summarize count() by cIP, csUriStem, sComputerName | where count_ > 1 index=iis (cs_uri_stem="*ToolPane.aspx*" OR cs_uri_stem="*/_vti_bin/*" OR cs_uri_stem="*/_api/web*") cs_method=POST (cs_username="-" OR cs_username="") | stats count BY c_ip cs_uri_stem s_computername | where count>1 Atomic Red Team Tests
Sends an unauthenticated POST request to the SharePoint ToolPane.aspx endpoint to generate the IIS log signature associated with CVE-2026-55040 exploitation attempts.
Command
curl -s -k -X POST "https://sharepoint.lab.local/_layouts/15/ToolPane.aspx?DisplayMode=Edit" -H "Referer: /_layouts/SignOut.aspx" -H "Content-Type: application/x-www-form-urlencoded" --data "MSOTlPn_Uri=test" -o /tmp/sp_toolpane_resp.txt Cleanup
rm -f /tmp/sp_toolpane_resp.txt Expected Telemetry
IIS W3C log entry showing a POST to /_layouts/15/ToolPane.aspx with an empty/'-' username and a 200/302 status code.
Expected Detection
The kql/spl unauthenticated-POST detections fire when request count exceeds the threshold from the source IP.
Issues multiple unauthenticated POSTs to the SharePoint REST _api endpoint to simulate the weak-authentication access pattern.
Command
for i in $(seq 1 5); do curl -s -k -X POST "https://sharepoint.lab.local/_api/web/lists" -H "Content-Type: application/json;odata=verbose" --data '{}' -o /dev/null; done Cleanup
echo "no artifacts to clean" Expected Telemetry
Five IIS log entries for POST /_api/web/lists with no authenticated username.
Expected Detection
KQL/SPL/QRadar/Sumo/Chronicle detections aggregate the burst and alert on request_count > 3.
Simulates the post-exploitation behavior of the SharePoint IIS worker process spawning a command shell, matching the endpoint-based detections.
Command
powershell.exe -NoProfile -Command "Start-Process -FilePath cmd.exe -ArgumentList '/c whoami'" Cleanup
powershell.exe -NoProfile -Command "Get-Process cmd -ErrorAction SilentlyContinue | Stop-Process -Force" Expected Telemetry
Process-creation event (Sysmon EID 1 / EDR ProcessRollup) showing cmd.exe with a parent of w3wp.exe (when run under the SharePoint app pool context).
Expected Detection
The elastic_eql and crowdstrike_cql detections fire on w3wp.exe spawning cmd.exe/powershell.exe.