Microsoft SharePoint Server Improper Input Validation (CVE-2026-32201)
Detects exploitation of CVE-2026-32201, an improper input validation vulnerability in Microsoft SharePoint Server. This vulnerability is actively exploited in the wild (CISA KEV) and allows attackers to send crafted HTTP requests to SharePoint endpoints to bypass input validation controls, potentially enabling unauthorized access, remote code execution, or data exfiltration. CWE-20 class vulnerabilities in SharePoint have historically been leveraged for initial access and lateral movement in enterprise environments.
Vulnerability Intelligence
KEV — Known ExploitedAffected Software
- Vendor
- Microsoft
- Product
- SharePoint Server
Weakness (CWE)
Timeline
- Disclosed
- April 14, 2026
CVSS
What is CVE-2026-32201 Microsoft SharePoint Server Improper Input Validation (CVE-2026-32201)?
Microsoft SharePoint Server Improper Input Validation (CVE-2026-32201) (CVE-2026-32201) maps to the Initial Access and Execution and Lateral Movement tactics — the adversary is trying to get into your network in MITRE ATT&CK.
This page provides production-ready detection logic for Microsoft SharePoint Server Improper Input Validation (CVE-2026-32201), covering the data sources and telemetry it touches: IIS Logs, Azure Diagnostics, Microsoft Sentinel W3CIISLog. The queries below are rated critical severity at medium confidence, and ship for 7 SIEM platforms — KQL, SPL, Elastic, QRadar, Sumo, YARA-L, LogScale.
MITRE ATT&CK
union W3CIISLog, AzureDiagnostics
| where TimeGenerated >= ago(7d)
| where (csUriStem has_any ("/_layouts/", "/_api/", "/sites/", "/_vti_bin/") or ResourceType =~ "MICROSOFT.SHAREPOINT")
| where (
(csMethod in~ ("POST", "PUT", "PATCH") and (csUriQuery contains "..%2F" or csUriQuery contains "%00" or csUriQuery contains "<script" or csUriQuery contains "javascript:"))
or (scStatus in (400, 500, 502, 503) and scBytes > 5000)
or csUriStem matches regex @"(?i)(/\.\./)|(;.*\.aspx)|(%2e%2e)|(//\w+)")
| extend ClientIP = coalesce(cIP, CallerIPAddress), UserAgent = coalesce(csUserAgent, "unknown")
| summarize RequestCount = count(), UniqueURIs = dcount(csUriStem), StatusCodes = make_set(scStatus), UserAgents = make_set(UserAgent) by ClientIP, bin(TimeGenerated, 5m)
| where RequestCount > 20 or UniqueURIs > 10
| project TimeGenerated, ClientIP, RequestCount, UniqueURIs, StatusCodes, UserAgents Detects anomalous HTTP request patterns against SharePoint endpoints indicative of CVE-2026-32201 exploitation, including encoded traversal sequences, null bytes, script injection payloads, and high-volume probing from single IPs.
Data Sources
Required Tables
False Positives
- Automated scanning tools or vulnerability scanners run by internal security teams
- Load balancer health checks generating high request volumes
- Legitimate SharePoint crawlers or search indexing services producing unusual URI patterns
- Penetration testing or red team exercises targeting SharePoint infrastructure
Sigma rule & cross-platform mapping
The detection logic for Microsoft SharePoint Server Improper Input Validation (CVE-2026-32201) (CVE-2026-32201) 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: azure Browse the community-maintained Sigma rules for this technique:
Platform-specific guides for CVE-2026-32201
Testing Methodology
Validate this detection against 4 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 1SharePoint Encoded Path Traversal Probe (CVE-2026-32201)
Expected signal: IIS W3C log entry with cs-uri-stem=/_layouts/15/start.aspx, cs-uri-query containing %2e%2e%2f, cs-method=POST, and HTTP status 400 or 500 (or 200 if vulnerable). Network connection event from test host to SharePoint server on TCP/80 or TCP/443.
- Test 2SharePoint REST API Null Byte Injection (CVE-2026-32201)
Expected signal: 10 IIS log entries to /_api/web/lists with POST method, JSON content-type, and null byte (%00) in request body. Windows Security Event 4688 should NOT appear unless RCE achieved. HTTP 400/401/403/500 expected in non-vulnerable or patched environments.
- Test 3SharePoint Webshell Drop via Exploited Upload Endpoint (CVE-2026-32201 Post-Exploitation Simulation)
Expected signal: Windows Security Event 4663 (File System Audit) for new .aspx file creation in SharePoint _layouts directory by process other than normal SharePoint setup. Sysmon Event ID 11 (FileCreate) with TargetFilename matching *.aspx in SharePoint web root paths. IIS log entry for GET request to /_layouts/15/detection_test_cve_2026_32201.aspx returning HTTP 200.
- Test 4High-Volume SharePoint Endpoint Fuzzing (CVE-2026-32201 Scanner Simulation)
Expected signal: 32+ IIS log entries across 4 SharePoint endpoints within ~7 seconds from single source IP. Encoded traversal sequences visible in cs-uri-query fields. Mix of HTTP 400, 403, 404, and 500 response codes expected.
Unlock Pro Content
Get the full detection package for CVE-2026-32201 including response playbook, investigation guide, and atomic red team tests.