WarrenBarr
SEC-01
Advisories
Published findings
OPS-02
Methodology
How an engagement runs
ENG-03
IT & Dev
Build and administer
ARM-04
Software
Tooling I wrote
MSP-05
MSSP
Flat-rate managed
REC-06
Case Studies
Work, in full
WEB-07
Websites
Sites that convert
SUP-08
Gear
Coming soon
DOC-09
Doctrine
What I will not do
WHO-10
About
Who you'd be hiring

Microsoft SharePoint Server — Four Active CVEs, CISA Hardening Alert
CVE-2026-56164 Zero-Day · CVE-2026-45659 Deserialization RCE · IIS Machine Key Theft · Malware Deployment

CVE-2026-56164 CVE-2026-45659 CVE-2026-32201 CVE-2026-58644 CISA KEV Zero-Day RCE Deserialization IIS Key Theft SharePoint On-Premises Actively Exploited
CISA issued a dedicated hardening alert for on-premises Microsoft SharePoint Server on July 14, 2026 — a relatively rare move that signals something beyond the normal patch-Tuesday advisory cadence. The alert identifies four CVEs being actively exploited in combination to gain unauthorized access, execute code, establish persistence, and deploy malware on SharePoint Server installations. Three of the four were already in CISA's KEV catalog; the fourth, CVE-2026-58644, was added July 16 as exploitation was confirmed.
The most urgent of the four is CVE-2026-56164, a zero-day discovered by Jayson Frost and Genwei Jiang of Mandiant and Google Cloud's FLARE Offensive Task Force — attribution that means it was found during active incident response, not during routine research. Microsoft assigned it a CVSS of 5.3 ("Moderate"). The National Vulnerability Database independently scored it 9.8 (Critical). It is unauthenticated, pre-auth, network-based, and requires no user interaction. CISA added it to KEV on the same day July Patch Tuesday patches shipped.
Microsoft's CVSS score of 5.3 is being unanimously criticized by the security industry. NVD scored it 9.8. It is unauthenticated, pre-auth, remote, no-click, and actively being exploited in the wild. Do not use the vendor CVSS score to prioritize this one. Patch on-premises SharePoint immediately and treat any internet-facing instance as potentially compromised.
CVE-2026-56164 — Microsoft CVSS 5.3 | NVD CVSS 9.8 — CWE-306 (Missing Authentication for Critical Function)
A missing authentication check for a critical SharePoint API function accessible over the network. An unauthenticated remote attacker can call this function and escalate privileges on the SharePoint Server. Found by Mandiant/FLARE during an active intrusion. CISA KEV July 14, 2026. Affects SharePoint Server 2016, 2019, and Subscription Edition.

CVE-2026-45659 — CVSS 8.8 — Deserialization of Untrusted Data (RCE)
A deserialization vulnerability that allows an authenticated attacker with minimum Site Member permissions to execute arbitrary code remotely on the SharePoint Server. No admin privileges required — a basic site account is enough. Patched in May 2026, CISA KEV July 1, 2026. Storm-2603 (Warlock ransomware operator) has been observed exploiting this alongside the unauthenticated flaws.

CVE-2026-32201 — CVSS not published — RCE
An earlier SharePoint RCE added to CISA KEV in April 2026. Attackers chaining this with the newer flaws for persistence and lateral movement.

CVE-2026-58644 — CVSS 9.8 — RCE
The highest-scored of the cluster. Added to CISA KEV July 16, 2026. Microsoft July Patch Tuesday fix. Chained with CVE-2026-56164 in observed attacks.

Affected: All supported on-premises SharePoint Server versions: Subscription Edition, 2019, and 2016
SharePoint Online (Microsoft 365): Not affected — this is an on-premises-only issue
CISA's hardening alert specifically calls out a post-exploitation technique that distinguishes these attacks from routine SharePoint compromises: IIS machine key theft. After gaining code execution on a SharePoint Server, attackers are extracting the IIS machine key from the server's configuration. The machine key is used by ASP.NET applications (including SharePoint) to protect session state, view state, and other sensitive data via encryption and HMAC signing.
With the machine key, an attacker can forge ViewState objects for any ASP.NET application on the server that shares the same key, enabling further deserialization attacks and code execution without valid credentials. This technique enables persistence that survives patching — even after the original vulnerability is remediated, a stolen machine key gives the attacker a persistent path back into the application.
CISA's alert notes that attackers are using this technique to "establish persistence and deploy malware" as a second-stage activity following initial access via the CVEs listed above.
Verify SharePoint Server patch level:
# In SharePoint Central Administration: # Upgrade and Migration → Review database status # Or via PowerShell: Add-PSSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue (Get-SPFarm).BuildVersion # Cross-reference against Microsoft's July 2026 build numbers for your edition
Hunt for IIS machine key theft indicators:
# Check IIS configuration for machine key values # If the machineKey in web.config or applicationHost.config # has validation/decryption keys, consider them potentially exposed # If exploitation is suspected, rotate them (see Remediation) # Look for unexpected access to web.config or applicationHost.config in IIS logs: Get-WinEvent -LogName "Security" | Where-Object { $_.Id -eq 4663 -and $_.Message -match "web.config|applicationHost" } | Select-Object TimeCreated, Message | Format-List
Hunt for webshells and unexpected files in SharePoint directories:
# SharePoint web root — look for recently modified ASPX files Get-ChildItem -Path "C:\inetpub\wwwroot\wss\" -Recurse -Include "*.aspx","*.asmx" | Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-30) } | Select-Object FullName, LastWriteTime # Check for files not matching expected SharePoint structure Get-ChildItem -Path "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\" ` -Recurse -Include "*.aspx","*.dll" | Where-Object { $_.LastWriteTime -gt (Get-Date).AddDays(-30) } | Select-Object FullName, LastWriteTime
Enable AMSI on SharePoint as an interim mitigation (CISA recommended):
# SharePoint 2019 and Subscription Edition support AMSI integration # This can detect and block malicious ViewState deserialization attempts # Enable via SharePoint Central Administration: # Security → General Security → Configure AMSI # PowerShell (Subscription Edition): $contentService = [Microsoft.SharePoint.Administration.SPWebService]::ContentService $contentService.AMSIEnabled = $true $contentService.Update()
CVEs active CVE-2026-56164 (pre-auth EoP), CVE-2026-45659 (deser RCE), CVE-2026-32201 (RCE), CVE-2026-58644 (RCE CVSS 9.8) Post-exploitation IIS machine key theft → forged ViewState → persistent RCE Threat actor Storm-2603 (Warlock ransomware) observed exploiting CVE-2026-45659 Discovery CVE-2026-56164 found by Mandiant/FLARE during live incident response CISA alert Dedicated SharePoint hardening advisory — July 14, 2026 Affected scope On-premises SharePoint Server 2016, 2019, Subscription Edition ONLY Not affected SharePoint Online (Microsoft 365)

Step 1 — Apply July 2026 Patch Tuesday updates to all SharePoint servers: Install the July 14, 2026 cumulative update for your SharePoint Server version. Note that SharePoint Server updates are separate from the Windows cumulative update — deploying the standard Windows update is not sufficient. SharePoint Server must be updated through its own servicing process.

Step 2 — Enable AMSI integration with Full Request Body Scan mode: CISA recommends this as an interim mitigation even before patching. It provides detection and blocking of malicious deserialization payloads in ViewState. See detection commands above.

Step 3 — Rotate IIS machine keys if exploitation is suspected: If your SharePoint Server was internet-accessible during the exposure window, rotate the machine key. This invalidates any stolen keys that could be used for persistent deserialization attacks. Generate a new key in IIS Manager → machine.config, or use PowerShell to set a new random key in the ASP.NET machine key configuration.

Step 4 — Take internet-facing SharePoint offline until patched: If you cannot immediately patch SharePoint 2016 or 2019 instances that are internet-accessible, take them offline or place a WAF in front of them. CISA specifically advises organizations on end-of-support SharePoint versions to accelerate migration planning.

Step 5 — SharePoint Server 2016 and 2019: Both are approaching or at end-of-support. These attacks are a strong forcing function for migration to SharePoint Subscription Edition or SharePoint Online. If migration is not imminent, internet isolation is the minimum acceptable control.

More like this, when it happens Advisories only. No newsletter, no marketing, unsubscribe in one click.

Barr Cyber — Application Security & Endpoint Hardening

On-premises SharePoint Server is a common finding in small and mid-sized organization assessments — often unpatched, internet-facing, and running on end-of-life versions. If your SharePoint environment has not been reviewed since this advisory, contact Barr Cyber.

Get in Touch →