1-minute read of a 5 min report

Two SharePoint Flaws Chain Into Unauthenticated Server Code Execution

By

1-minute read

What a defender needs to know

VulnCheck published a technical walkthrough of a complete Microsoft SharePoint exploit chain. CVE-2026-55040 forges a SharePoint service-to-service identity; CVE-2026-63520 uses unsafe .NET type instantiation in Business Connectivity Services to execute code as the SharePoint site service account. Together they provide unauthenticated server code execution.

On August 25, Defused observed honeypot traffic exercising the identity bypass, enumerating administrators, and probing the Business Data Catalog sink behind CVE-2026-63520. It observed no code execution. CISA confirms exploitation only of CVE-2026-55040 and does not say attacks also used the complete chain. Microsoft fixed the authentication bypass in July and the execution flaw on August 11. The RCE affects every supported SharePoint version and certain Project Server and Office Web Apps Server versions, while the authentication bypass affects SharePoint only.

Verify every SharePoint server at Subscription Edition build 16.0.19725.20522, SharePoint 2019 build 16.0.10417.20198, SharePoint 2016 build 16.0.5565.1001, or a later cumulative build. Run (Get-SPFarm).BuildVersion.ToString() in the SharePoint Management Shell and confirm a consistent farm result. Inventory Project Server and Office Web Apps Server separately against Microsoft’s CVE-2026-63520 product table.

For previously exposed farms, correlate IIS and ULS requests that become a privileged identity without expected authentication with administrator enumeration, unexpected Business Data Catalog model activity, /_vti_bin/client.svc/ProcessQuery, and child processes from SharePoint workers. A current build on every farm server and no unexplained identity-to-catalog-to-process sequence is the expected verification result.

Primary sources