SharePoint Security in 2026: Exploit Chains and Patch Guidance
Executive Summary
Microsoft SharePoint Server has faced a sustained series of actively exploited vulnerabilities throughout 2026. What gained widespread attention in July with CVE-2026-56164 has continued through additional authentication bypasses, remote code execution vulnerabilities, and new attack chains disclosed in August and September.
Between April and September 2026, CISA added seven Microsoft SharePoint vulnerabilities to its Known Exploited Vulnerabilities (KEV) catalog. On November 10, Microsoft released another SharePoint security update, addressing even more vulnerabilities, including CVE-2026-120002, a critical privilege-escalation flaw rated 9.9.
The risk is real for organizations running on-premises SharePoint Server 2016 or 2019, both of which reached the end of Microsoft’s standard support lifecycle in July 2026. SharePoint Server Subscription Edition is still technically supported, but requires continued patching, hardening, and monitoring.
For credit unions, banks, registered investment advisers, healthcare organizations, school districts, government agencies, and other businesses, the priorities are pretty clear: establish which SharePoint systems exist, verify current security updates, investigate possible compromise, and eliminate unsupported infrastructure.
Remember, a patched server isn’t necessarily a clean server.
How the SharePoint Attacks Developed Throughout 2026
The July incident was not one isolated vulnerability or a single, universally documented four-CVE exploit chain. Multiple vulnerabilities were disclosed and exploited across separate periods, with researchers also demonstrating specific combinations capable of bypassing authentication and executing malicious code.
The verified timeline shows how the exposure expanded.
| Vulnerability | Verified significance |
|---|---|
| CVE-2026-32201 | Improper input validation allowing spoofing. CVSS 6.5. Patched and added to CISA KEV on April 14. |
| CVE-2026-45659 | Deserialization vulnerability allowing authenticated remote code execution. CVSS 8.8. Patched in May; added to KEV July 1. |
| CVE-2026-56164 | Missing authentication for a critical function, allowing unauthenticated privilege escalation. CVSS 9.8. Patched and added to KEV July 14. |
| CVE-2026-58644 | Deserialization vulnerability allowing unauthenticated remote code execution. CVSS 9.8. Patched July 14; added to KEV July 16. |
| CVE-2026-50522 | Critical remote code execution vulnerability. CVSS 9.8. Researchers observed exploitation and machine-key theft in July; added to KEV July 22. |
| CVE-2026-55040 | Authentication bypass involving SharePoint’s token validation. CVSS 9.1. Patched July 14; added to KEV August 18. |
| CVE-2026-63520 | Remote code execution vulnerability. CVSS 8.1. Patched August 11; demonstrated in a chain with CVE-2026-55040. Subsequent exploitation attempts were reported. |
| CVE-2026-65660 | Code injection enabling authenticated remote code execution. CVSS 8.8. Patched August 11; added to KEV September 25. |
| CVE-2026-120002 | Critical privilege escalation vulnerability. CVSS 9.9. Disclosed and patched November 10. Publicly confirmed exploitation had not been established as of this update. |
These vulnerabilities don’t share identical exploitation requirements or represent one continuous attack technique. Some of these permit unauthenticated actions, while others require an existing account or can become more dangerous when combined with another vulnerability.
That matters when assessing whether a particular SharePoint environment was exposed.
Sources: CISA’s July SharePoint alert, CERT-EU’s July advisory, and the Microsoft Security Update Guide.
The August Exploit Chain Changed the Risk
One of the most consequential developments occurred after the original July reporting. Security researchers at Rapid7 discovered two SharePoint weaknesses that could be chained together to achieve unauthenticated remote code execution.
The first, CVE-2026-55040, involves weaknesses in the validation of JSON Web Tokens. It can allow an unauthenticated attacker to impersonate a SharePoint user, potentially including an administrator.
The second, CVE-2026-63520, involves improper input validation in SharePoint’s Business Connectivity Services. Combined with the authentication bypass, it can provide a path from external access to code execution on a vulnerable server.
Microsoft addressed the authentication bypass in July and the remote code execution component in August, while Rapid7 published technical details for the authentication bypass on August 11. Subsequent public research and government advisories documented exploitation attempts involving these weaknesses, and CISA added CVE-2026-55040 to its KEV catalog on August 18.
This development reinforced a critical lesson from the July incidents: a vulnerability that does not independently provide complete system compromise can become substantially more dangerous when combined with another weakness.
The September exploitation of CVE-2026-65660 reinforced the same concern. Although the underlying vulnerability requires authenticated access, investigators documented conditions in which it could be combined with other weaknesses to expand the attacker’s capabilities.
November 2026: SharePoint Still Requires Immediate Attention
Microsoft’s November 10, 2026 security release demonstrates why organizations cannot treat the July remediation effort as complete.
The November cumulative update for SharePoint Server Subscription Edition, KB5002945, addresses additional security vulnerabilities involving remote code execution, privilege escalation, information disclosure, spoofing, and security-feature bypasses.
Among them is CVE-2026-120002, rated 9.9 under CVSS v3.1. Microsoft identifies it as an incorrect-authorization vulnerability that can allow an authenticated attacker to elevate privileges over a network.
As we’ve mentioned many times, a high CVSS score doesn’t establish that exploitation has occurred, nevertheless, the vulnerability warrants prompt remediation because of its potential impact.
As of November 11, 2026, Microsoft’s published update information identifies the following current SharePoint Server Subscription Edition package:
KB5002945 | Build 16.0.20326.20278 | Released November 10, 2026
Administrators should validate successful deployment across the entire farm and check Microsoft’s installation prerequisites and known issues. Organizations using SharePoint Workflow Manager have additional deployment requirements.
Microsoft also warns that legacy SharePoint 2010 workflows and InfoPath Forms Services have reached the end of support, creating additional migration concerns for organizations still dependent on older business processes.
SharePoint Server 2016 and 2019: The End-of-Support Problem
Microsoft’s published lifecycle schedule identifies July 2026 as the end of extended support for SharePoint Server 2016 and 2019.
Microsoft did publish August 2026 updates for those products after the announced lifecycle deadline, but their availability should not be interpreted as a restoration of ongoing product support or a guarantee of future security updates.
Organizations operating these versions need a documented transition plan.
The supported choices generally include SharePoint Server Subscription Edition, SharePoint Online within Microsoft 365, or an appropriately designed hybrid environment.
SharePoint Online is not affected by the specific on-premises SharePoint Server vulnerabilities discussed in the July and August advisories. However, moving to Microsoft 365 does not eliminate responsibilities for identity security, access permissions, data governance, and third-party integrations.
For organizations retaining on-premises infrastructure, support status must be considered alongside patching, external exposure, logging, and the ability to investigate security incidents.
The relevant question for leadership is whether the organization can justify the ongoing risk of relying on an unsupported platform.
The Technical Side: Why Machine-Key Theft Matters
Several of the SharePoint exploitation reports involve the theft of ASP.NET machine keys associated with Internet Information Services (IIS).
These cryptographic keys support security functions like the validation of ASP.NET ViewState. If attackers obtain the relevant key material, they might be able to forge data that the application treats as trusted, supporting further exploitation or persistence.
This creates a problem that a software update alone can’t necessarily resolve.
Installing security updates can prevent the exploitation of the underlying fixed vulnerabilities, but it doesn’t automatically invalidate keys that were already stolen or remove malicious files and persistence mechanisms.
CISA specifically recommends investigating and removing intrusion artifacts, including machine-key harvesting tools, before rotating affected keys. Otherwise, attackers with continued access might be able to steal replacement keys.
Security teams should also investigate web shells, suspicious activity involving SharePoint’s IIS worker processes, unexpected privilege changes, and unauthorized administrative or remote-access activity.
CISA has published SharePoint-specific AMSI and Microsoft Defender detections to support this. It also recommends enabling SharePoint’s Antimalware Scan Interface integration with Request Body Scan Mode set to Full Mode where operationally feasible.
These controls improve visibility and protection, but they are not substitutes for patching and compromise assessment.
What Regulated Organizations Need to Document
The regulatory implications differ by industry, as usual. A SharePoint vulnerability does not automatically establish a reportable breach or violation of a particular regulation. However, a known exploited vulnerability affecting systems that maintain sensitive information creates a significant risk-management and documentation obligation.
Credit Unions and Banks
Credit unions should evaluate affected SharePoint infrastructure within their existing information-security and incident-response programs.
Under NCUA’s cyber-incident notification rule, federally insured credit unions must notify the NCUA as soon as possible and within 72 hours after reasonably believing they have experienced a reportable cyber incident. Discovering an unpatched SharePoint server does not, by itself, trigger that reporting deadline.
Banks must evaluate their own applicable federal and state cybersecurity requirements, including relevant incident-notification obligations.
For both sectors, evidence of patch verification, exposure assessment, third-party responsibilities, and investigation findings can help demonstrate appropriate risk management.
NCUA cyber-incident notification guidance.
Registered Investment Advisers and Wealth Management Firms
The SEC’s amended Regulation S-P has introduced more explicit incident-response and customer-information safeguarding requirements for covered institutions.
A suspected SharePoint compromise involving customer information should therefore be evaluated under the firm’s written incident-response program, including the potential need for customer notification and service-provider coordination.
The amended rule generally requires affected-individual notification as soon as practicable, but no later than 30 days after awareness of an incident involving unauthorized access to or use of customer information, where the rule’s notification conditions are satisfied.
An unpatched system alone doesn’t necessarily establish that those conditions have been met.
SEC Regulation S-P amendments.
Healthcare Organizations
Healthcare organizations and business associates subject to HIPAA must account for relevant threats and vulnerabilities in their security risk analysis and implement appropriate risk-management measures.
SharePoint environments storing or processing electronic protected health information should be included in that assessment, including systems operated by vendors.
Where compromise is suspected, organizations should follow their security-incident procedures, document the investigation and evaluate whether a breach notification obligation exists.
HIPAA does not automatically require breach notification solely because a vulnerability was present.
HHS guidance on HIPAA security risk analysis.
Schools, Government, and Other Organizations
For school districts and higher-education institutions, compromised SharePoint infrastructure could affect student and employee records, administrative workflows, and operational continuity.
Government agencies must evaluate their applicable cybersecurity directives. CISA’s Binding Operational Directive 26-04 requires Federal Civilian Executive Branch agencies to prioritize remediation according to factors including internet exposure, known exploitation, exploit automation, and technical impact.
The accelerated deadlines appearing in CISA’s KEV catalog are federal requirements under the directive, not universal private-sector patching deadlines.
Manufacturers, professional services firms, and other businesses face similar operational concerns even when a specific federal cybersecurity regulation does not apply.
Across industries, the governing principle is the same: the organization must understand its exposure, assign responsibility, and maintain evidence supporting its decisions.
The SharePoint Remediation and Verification Playbook
Organizations that still operate SharePoint Server should complete a documented review of the following areas.
1. Identify every SharePoint Server environment.
Inventory production, development, test, disaster-recovery, and third-party-hosted installations. Verify the version, build number, internet exposure, business owner, and whether sensitive information is stored or processed.
2. Verify current security updates.
For supported SharePoint Server Subscription Edition deployments, validate the latest applicable Microsoft cumulative security update, including successful farm configuration and post-installation checks.
For SharePoint Server 2016 and 2019, verify available updates as an interim protective measure while pursuing migration. Installing the latest available legacy update does not restore a supported status.
3. Reduce external exposure.
Eliminate unnecessary direct internet access. Where external connectivity is required, CISA recommends an authenticated Layer 7 reverse proxy or equivalent application-layer security control capable of inspecting and filtering requests.
Restrict SharePoint Central Administration and other management interfaces.
4. Investigate possible compromise.
Review retained IIS, SharePoint, Windows, identity, and endpoint-security telemetry, especially for periods when a server was exposed and vulnerable.
Investigate suspicious web shells, unexpected processes or scheduled tasks, machine-key access, unusual account activity, and unauthorized remote-access tools.
Preserve evidence and involve an incident-response specialist when indicators suggest an intrusion.
5. Remediate persistence and compromised secrets.
Where compromise is identified or machine-key exposure is suspected, remove malicious artifacts and unauthorized access before rotating affected machine keys and other compromised credentials.
Follow Microsoft’s supported key-management and IIS procedures, and verify that attackers can’t reacquire the replacement material.
6. Document the outcome and assign ongoing ownership.
Record affected assets, update status, exposure history, investigative evidence, containment decisions, remaining risks, and any applicable notification assessment.
Assign an accountable owner for continued monitoring, patching, and legacy-system replacement.
A vulnerability scan or successful patch installation can demonstrate part of this work. Neither automatically proves that the environment was never compromised.
Why This Matters Beyond SharePoint
The bigger lesson from 2026 is that internet-facing business systems need continuous ownership throughout their lifecycle, including the periods immediately before and after vendor support ends.
The 2025 ToolShell campaign demonstrated how attackers could exploit SharePoint weaknesses to obtain access and establish persistence. Microsoft’s investigation at that time identified activity involving Linen Typhoon, Violet Typhoon, and Storm-2603, including ransomware deployment.
For executives, the larger issue is operational accountability. An organization may have a functioning help desk, successful backups, and a completed patching report while still lacking reliable oversight of externally exposed servers, stolen credentials, and unsupported platforms.
Unfortunately, those gaps often become visible only after an incident.
A strong managed IT and cybersecurity program connects vulnerability management, security monitoring, identity protection, incident response, and lifecycle planning into one accountable operation.
TorchLight Secured & Managed IT helps organizations evaluate exposed infrastructure, validate remediation, investigate suspicious activity, and establish accountable security and IT operations.
For organizations uncertain about their SharePoint environment, a focused security assessment can clarify existing exposure and establish the next steps before another vulnerability becomes an incident.
Contact TorchLight to discuss SharePoint security, managed detection and response, or infrastructure modernization.
Primary Sources and Technical References
- CISA: SharePoint hardening after new exploitations, July 14, 2026
- CERT-EU: Critical vulnerabilities in Microsoft SharePoint, July 2026
- CISA: KEV additions, August 18, 2026
- CISA: KEV additions, September 25, 2026
- Microsoft: November 10, 2026 SharePoint security update
- Microsoft: SharePoint Server update history
- Rapid7: CVE-2026-55040 authentication bypass research
- Canadian Centre for Cyber Security: CVE-2026-65660 advisory
- Microsoft: July 2025 ToolShell threat-actor investigation
- CISA: Binding Operational Directive 26-04
Still Running SharePoint? Let’s Make Sure You’re Covered.
Whether you’re concerned about recent vulnerabilities, managing an aging SharePoint environment, or planning a migration to SharePoint Online or Microsoft 365, TorchLight can help you determine the safest and most practical path forward.
Our team can help assess your current environment, investigate potential exposure, manage SharePoint migrations, and provide the ongoing IT and security support your organization needs. You don’t have to figure it all out before reaching out.
