Executive Summary
During the August 2026 Patch Tuesday cycle, Rapid7 Labs and Microsoft engaged in a critical coordinated disclosure regarding a severe remote code execution (RCE) vulnerability in Microsoft SharePoint Server. Identified as CVE-2026-63520, this High-severity flaw (CVSS 8.1) originates from unsafe .NET type instantiation within the Business Connectivity Services (BCS) component of SharePoint.
In a sophisticated demonstration of modern offensive security research, Rapid7 researchers successfully chained CVE-2026-63520 with a companion authentication bypass flaw, CVE-2026-55040. This combination enables unauthenticated network actors to achieve complete remote code execution against on-premises SharePoint enterprise servers. Notably, the entire exploit chain was uncovered and refined through an autonomous agentic LLM workflow. Guided by human security researchers, the AI system accumulated 120 hours of agent runtime across 96 sessions, executing approximately 80,000 tool calls and 256 prompts over a 24-day period. This research was originally developed for entry into Pwn2Own Berlin.
Deep-Dive Technical Analysis
1. Root Cause: Unsafe .NET Type Instantiation in Business Connectivity Services
SharePoint's Business Connectivity Services (BCS) are designed to facilitate the integration of external data sources and application definitions into the SharePoint environment. The vulnerability lies in the way BCS processes these definitions.
The underlying issue is found within the deserialization and dynamic type-instantiation routines. These routines fail to adequately validate user-supplied input against restricted type binders or strict allowlists. This lack of validation allows an attacker to provide a specially crafted XML or JSON definition that specifies arbitrary .NET types. By selecting types with parameterized constructors or leveraging existing gadget chains, an attacker can force the server to execute arbitrary system commands the moment the malicious type is instantiated in memory.
2. Chaining with CVE-2026-55040 for Unauthenticated Remote Compromise
Achieving remote code execution typically requires a foothold or valid credentials. However, Rapid7 bypassed this requirement by utilizing a two-stage attack chain:
* Stage 1 (Authentication Bypass - CVE-2026-55040): This stage exploits fundamental flaws in URL routing and ASP.NET request handler authorization. These flaws permit external, unauthenticated actors to reach internal BCS management and synchronization endpoints that should otherwise be protected by mandatory authentication layers.
* Stage 2 (Remote Code Execution - CVE-2026-63520): Once the BCS endpoint is reached, the unauthenticated attacker transmits the malicious .NET type payload. The server processes the request, triggering immediate code execution. This execution occurs under the security context of the SharePoint Web Application Pool identity, which is frequently a high-privilege domain or service account, leading to total server compromise.
3. The Methodology: Autonomous Agentic AI Vulnerability Research
The discovery of this chain represents a significant shift in vulnerability research methodology. Rapid7 utilized an agentic LLM framework designed to operate with autonomous tool calls and iterative feedback loops. This framework allowed the AI to:
* Map the vast attack surface of SharePoint's complex architecture.
* Iteratively generate and test candidate payloads.
* Identify and overcome complex .NET serialization barriers that might have taken human researchers significantly longer to navigate manually.
This high-frequency, iterative approach underscores the growing capability of AI to assist in discovering deep architectural flaws in enterprise software.
Affected Products and Attack Surface
The following products are confirmed to be affected by these vulnerabilities:
Affected Product
Version / Edition
Microsoft SharePoint Server
Subscription Edition
Microsoft SharePoint Server
2019
Microsoft SharePoint Enterprise Server
2016
Microsoft Project Server
2013 SP1 (64-bit)
Microsoft Office Web Apps
2013 SP1
Industry Impact and Threat Landscape
On-premises SharePoint servers remain high-value "crown jewels" for any organization. They house corporate intranets, classified internal documentation, sensitive financial filings, and critical internal directories. The disclosure of an unauthenticated RCE chain poses a severe risk, as automated threat actors are likely to rapidly reverse-engineer patch diffs to develop wormable exploits. Given the prevalence of SharePoint in the enterprise, the speed of remediation is paramount to preventing widespread exploitation.
Mitigation Strategies and Practical Recommendations
Enterprise IT and SOC teams should prioritize the following actions to defend against this exploit chain:
1. Immediate Patching: Apply the August 2026 Microsoft Security Updates immediately to all SharePoint server farms and Office Web Apps instances. Consult the Microsoft Patch Tuesday Advisory for specific deployment details.
2. Network Perimeter Security: Restrict external network access to SharePoint management interfaces. Organizations should enforce Zero Trust Network Access (ZTNA) or require a corporate VPN for all administrative and management traffic.
3. Service Account Hardening: Isolate SharePoint Application Pool service accounts. Ensure these accounts adhere to the principle of least privilege within Active Directory to limit the impact of a potential compromise.
4. WAF Implementation: Deploy Web Application Firewall (WAF) signatures specifically tuned to detect anomalous traffic targeting BCS endpoints and malformed .NET type declarations.
5. Enhanced Monitoring: Review Windows Event Logs and IIS logs for unauthorized access attempts to internal BCS handlers. Security teams should specifically monitor for abnormal child processes spawned by w3wp.exe, such as cmd.exe or powershell.exe.
For a more granular technical breakdown, refer to the Rapid7 Labs Analysis.