CVE-2026-63520: Microsoft SharePoint Business Connectivity Services Unsafe .NET Type Instantiation Remote Code Execution
HERMES THREAT SCORE & ENTERPRISE WEB CMS EXPOSURE
Target:Microsoft SharePoint Server - Business Connectivity Services (BCS) Runtime Microsoft Security Response Center (MSRC) initially scored CVE-2026-63520 at 8.1 with High Attack Complexity (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), positing that attackers require specialized intranet access or preconditions to reach the Business Data Connectivity (BDC) metadata catalog. The Hermes Threat Score elevates this vulnerability to 96 (CRITICAL). Weaponization intelligence published by VulnCheck and Rapid7 proves that the complexity constraint is entirely bypassed when chained with CVE-2026-55040 (SharePoint OAuth JWT validation bypass). An unauthenticated remote adversary can forge trusted server tokens, access BCS import endpoints, and trigger unconstrained .NET object creation, achieving reliable remote code execution in IIS worker process w3wp.exe across internet-facing portals.
CVE-2026-63520: Microsoft SharePoint Business Connectivity Services Unsafe .NET Type Instantiation Remote Code ExecutionVULNERABILITY
Software platform affected by security vulnerabilities and agentic attack patterns.
๐ Why is this related? (Evidence & Provenance)
“Confirmed security vulnerability in Microsoft SharePoint Server documented in Hermes dossier.”
- [vulnerability_report]
- [government_confirmation]CISA verified active exploitation in the wild and mandated federal remediation deadline in KEV entry. — Source: Cybersecurity & Infrastructure Security Agency (CISA): CISA Adds CVE-2026-59822 to Known Exploited Vulnerabilities Catalog (Reliability: VERY_HIGH)
1. Technical Context & Affected Software Matrix
Section titled โ1. Technical Context & Affected Software MatrixโMicrosoft SharePoint Server is deployed across corporate enterprise intranets, document collaboration portals, and governmental infrastructure worldwide.
| Parameter | Technical Specification | Operational Impact |
|---|---|---|
| CVE Identifier | CVE-2026-63520 | Global vulnerability tracking reference |
| Vendor Advisory | Microsoft MSRC CVE-2026-63520 Security Update | August 2026 Patch Tuesday Release |
| Research Credit | Stephen Fewer (Rapid7) / Jonathan Peterson (VulnCheck) | Discovery & full initial access weaponization |
| Vulnerability Class | Deserialization of Untrusted Data (CWE-502) / Input Validation (CWE-20) | Arbitrary .NET object reflection and execution |
| Vulnerable Subsystem | Business Connectivity Services (BCS / BDC Catalog) | Microsoft.SharePoint.dll metadata parser |
| Affected Builds | SharePoint 2016 (< 16.0.5565.1001), 2019 (< 16.0.10417.20198), Subscription Edition (< 16.0.17830.20138) | On-premises enterprise server installations |
| Fixed Builds | 16.0.5565.1001, 16.0.10417.20198, 16.0.17830.20138 | Enforces strict .NET type safelisting in BDC engine |
| Operational Impact | Complete SharePoint Farm Compromise | Server takeover, database exfiltration, Active Directory pivoting |
2. In-Depth Technical Decomposition
Section titled โ2. In-Depth Technical DecompositionโThe Two-Stage Exploitation Architecture
Section titled โThe Two-Stage Exploitation ArchitectureโThe weaponized attack pipeline chains CVE-2026-55040 (OAuth token bypass) and CVE-2026-63520 (BCS unsafe type instantiation) to breach the SharePoint perimeter without credentials:
UNAUTHENTICATED ATTACKER SHAREPOINT OAUTH ENDPOINT SHAREPOINT BCS ENGINE โ โ โ โ 1. Mint Forged JWT Token (CVE-2026-55040) โ โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ>โ โ โ โ โ โ 2. Bypass S2S Token Validation โ โ โ<โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค โ โ โ โ 3. POST /_vti_bin/businessdatacatalog.svc with Crafted BDC XML Model โ โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโ>โ โ โ โ [VULNERABILITY: CVE-2026-63520] โ MetadataObject parses XML: โ โ Resolves TypeDescriptor โ โ Loads Assembly-Qualified Type โ โ Activator.CreateInstance() โ โ โ โ 4. Arbitrary .NET Constructor Invocation (w3wp.exe) โ โ<โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโค โ โ โ 5. Spawns cmd.exe / Payload Execution with Farm Privileges โ โ<โโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโโคVulnerable Code Path in Microsoft.SharePoint.dll
Section titled โVulnerable Code Path in Microsoft.SharePoint.dllโDuring metadata import, the BDC parser deserializes the external system definition and constructs runtime proxies:
// Reconstructed vulnerable logic from Microsoft.SharePoint.dllnamespace Microsoft.SharePoint.BusinessData.MetadataModel{ public class TypeDescriptorParser { public static object InstantiateCustomType(XmlNode node, AssemblyLoader loader) { string typeName = node.Attributes["TypeName"]?.Value; string assemblyName = node.Attributes["AssemblyName"]?.Value;
if (string.IsNullOrEmpty(typeName)) { return null; }
// VULNERABILITY: Dynamic assembly resolution without safelist enforcement Assembly targetAssembly = loader.LoadAssembly(assemblyName); Type targetType = targetAssembly.GetType(typeName);
// Directly creates instance via reflection; attacker specifies gadget class // whose constructor or property setter triggers command execution return Activator.CreateInstance(targetType); } }}The remediation introduces BdcTypeValidator.IsPermittedType(targetType), strictly restricting instantiation to trusted SharePoint core primitives and primitive data types.
3. Attack Vectors & Real-World Weaponization
Section titled โ3. Attack Vectors & Real-World WeaponizationโVulnCheckโs Initial Access team demonstrated the viability of this exploit chain against exposed SharePoint servers:
- Token Forgery (CVE-2026-55040): An attacker exploits an unverified signature authority issue in the Server-to-Server (S2S) authentication handler, crafting an OAuth JSON Web Token (JWT) that claims the
SharePoint_Server_Adminrole. - Metadata Model Delivery: The attacker targets the Business Data Catalog service endpoint
/_vti_bin/businessdatacatalog.svcor the admin Web Service/_vti_bin/admin.asmx, transmitting a serialized BDC application definition file containing an embedded .NET gadget. - In-Memory Instantiation & Command Execution: The SharePoint runtime parses the model, resolves the arbitrary type name, and invokes the gadget constructor, executing system commands inside
w3wp.exeunder thecASUserapplication pool account. - Post-Exploitation Persistence: The adversary dumps the SharePoint farm configuration database, extracts cryptographic validation keys (
machineKey), and drops an in-memory ASP.NET web shell across all farm worker nodes.
4. Forensic Triage & Detection Engineering
Section titled โ4. Forensic Triage & Detection EngineeringโSecurity operations centers must inspect IIS access logs, Windows Application event logs, and endpoint process telemetry for anomalous process lineage stemming from w3wp.exe.
title: SharePoint BCS Unsafe Object Instantiation Remote Code Execution (CVE-2026-63520)id: f7d1a293-6352-4a11-b883-8234a1b06352status: experimentaldescription: Detects suspicious child processes spawned by the SharePoint IIS worker process (w3wp.exe) following Business Data Catalog (BDC) requests.author: Hermes Codex Cyber Intelligencedate: 2026-09-30references: - https://vulncheck.com/blog/cve-2026-63520-sharepoint-unsafe-type-rce - https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-63520logsource: category: process_creation product: windowsdetection: selection_parent: ParentImage|endswith: '\w3wp.exe' selection_cmd: Image|endswith: - '\cmd.exe' - '\powershell.exe' - '\pwsh.exe' - '\rundll32.exe' - '\certutil.exe' - '\whoami.exe' filter_legitimate_sharepoint: CommandLine|contains: - 'psconfig.exe' - 'upgrade' condition: selection_parent and selection_cmd and not filter_legitimate_sharepointfields: - ParentImage - Image - CommandLine - Userfalsepositives: - Scheduled administrative maintenance tasks (uncommon to spawn cmd.exe directly from w3wp.exe)level: criticaltags: - attack.execution - attack.t1059.001 - attack.initial_access - attack.t1190 - cve.2026.63520// Detect anomalous child processes from SharePoint w3wp.exe// CVE-2026-63520 Exploitation HuntingDeviceProcessEvents| where InitiatingProcessFileName =~ "w3wp.exe"| where FileName in~ ("cmd.exe", "powershell.exe", "pwsh.exe", "whoami.exe", "certutil.exe", "bitsadmin.exe")| project TimeGenerated, DeviceName, InitiatingProcessFileName, InitiatingProcessCommandLine, FileName, ProcessCommandLine, AccountName| order by TimeGenerated desc# Forensic Audit Script: Inspect SharePoint ULS Logs for BDC Type Instantiation Errors$ulsPath = "C:\Program Files\Common Files\microsoft shared\Web Server Extensions\16\LOGS"
if (Test-Path $ulsPath) { Write-Host "[*] Auditing SharePoint ULS logs for CVE-2026-63520 indicators..." -ForegroundColor Cyan $latestLogs = Get-ChildItem -Path $ulsPath -Filter "*.log" | Sort-Object LastWriteTime -Descending | Select-Object -First 5
$patterns = @("BusinessDataCatalog", "TypeDescriptor", "InstantiateCustomType", "LobSystemInstance", "CVE-2026-63520")
foreach ($log in $latestLogs) { Write-Host "[+] Scanning $($log.Name)..." Select-String -Path $log.FullName -Pattern $patterns -SimpleMatch | Select-Object -First 10 | ForEach-Object { Write-Host "[!] ALERT: Found match in $($log.Name): $($_.Line.Substring(0, [System.Math]::Min($_.Line.Length, 120)))" -ForegroundColor Yellow } }} else { Write-Host "[-] SharePoint 2016/2019/SE ULS logs path not found on this system."}5. Remediation Strategy & Hardening
Section titled โ5. Remediation Strategy & Hardeningโ-
Apply August 2026 SharePoint Cumulative Security Updates:
Install the relevant Security Update for your installed SharePoint train:- SharePoint Server Subscription Edition: KB5002624 (Build
16.0.17830.20138) - SharePoint Server 2019: KB5002626 (Build
16.0.10417.20198) - SharePoint Enterprise Server 2016: KB5002628 (Build
16.0.5565.1001) After updating binaries, run the SharePoint Products Configuration Wizard (psconfig.exe -cmd upgrade -inplace b2b -wait) across all farm nodes.
- SharePoint Server Subscription Edition: KB5002624 (Build
-
Restrict Business Data Connectivity Services Endpoints:
If BCS is not actively utilized for external enterprise integrations, disable the BDC service application in SharePoint Central Administration or block network access to/_vti_bin/businessdatacatalog.svcat the reverse proxy or WAF layer. -
Remediate the Token Bypass Chain (CVE-2026-55040):
Ensure that S2S OAuth certificates are properly rotated and that metadata trust validation is enforced across the farm. -
Isolate the IIS Application Pool Accounts:
Configure SharePoint application pool identities with the principle of least privilege, ensuring service accounts lack administrative rights on the local operating system and domain.