CVE-2026-45659: SharePoint authenticated remote code execution
Tech GuruQuick Answer
CVE-2026-45659 requires an authenticated attacker with at least SharePoint Site Member permissions and can lead to remote code execution. CISA records known ransomware-campaign use, so preserve site-membership, IIS, SharePoint and endpoint evidence while updating each farm server. The May CVRF supplies the edition-specific fixes below; membership review is useful but is not a patch, and catalog evidence does not prove that this farm was attacked.
Fix Or Immediate Action
What to do now: Install the newest applicable cumulative SharePoint security update across the farm and verify all servers and components.
Evidence check: CISA KEV catalog 2026.10.02 was checked on October 2. Vendor evidence and any unresolved fix limits are described below. Catalog inclusion confirms reported exploitation, not compromise of this deployment; verify current updates before production changes.
Context
Scope And Impact In Plain Language
Who should check: Anyone who manages Microsoft SharePoint Server.
When this applies: Only when the exact product, version, and required configuration match the live vendor advisory. Owning the product family alone does not mean the device is vulnerable.
What could happen: A successful attacker may be able to run attacker-chosen commands or software on the affected system, subject to the access and configuration requirements in the advisory.
Not sure? Find the product name and version in the device or application, then compare them with the affected-products section of the linked vendor notice.
Status At A Glance
| Product scope | Microsoft — SharePoint Server |
|---|---|
| CVE | CVE-2026-45659 |
| TechGeeks response tier | P0 — confirm an exact match and act now |
| CISA KEV added | 2026-07-01 |
| Vendor severity | Important |
| CVSS | 8.8 (CVSS v3.1 base) |
| Ransomware field | Known — CISA currently associates this CVE with known ransomware-campaign use. |
| Forensic-triage field | Yes — CISA's record calls for forensic triage. |
| CWE | CWE-502 |
| Federal remediation date | 2026-07-04 — applies to covered federal agencies; other organizations should set a risk-based deadline. |
What Happened
Microsoft SharePoint Server Deserialization of Untrusted Data Vulnerability. Microsoft SharePoint Server contains a deserialization of untrusted data vulnerability which allows an authorized attacker to execute code over a network. CISA's KEV listing confirms exploitation evidence, but it does not state how widespread the activity is or prove that any particular installation was compromised.
Affected Scope
On-premises SharePoint Server 2016, SharePoint Server 2019, and SharePoint Server Subscription Edition where listed by Microsoft; exploitation requires an authorized SharePoint context such as a Site Member.
Match the exact edition, hardware or virtual platform, release, patch level, enabled feature, and management exposure. A product-family name alone is not enough to establish applicability.
Steps
What To Do Now
- Confirm. Inventory every SharePoint Server asset and record its exact version, patch level, role, relevant configuration, and exposure.
- Preserve. Save UTC timestamps, off-device authentication, firewall, proxy, DNS, endpoint, application, and SIEM evidence before logs rotate or a disruptive change removes context.
- Contain. Restrict unnecessary internet and management-plane access using supported controls. Follow the live advisory: Open the live Microsoft advisory.
- Remediate. Install the newest applicable cumulative SharePoint security update across the farm and verify all servers and components.
- Validate. Verify the resulting version or patch level, service health, logging, expected access, an expected denial, and representative dependent workflows.
- Escalate. If exposure overlapped the vulnerable period or evidence is suspicious, treat the system as a potential incident and follow vendor and incident-response recovery guidance.
Fixed Releases And Mitigation
Permanent Fix
Microsoft's May 26 revision says the CVE was inadvertently omitted from the May security list, not that an additional patch was required for customers who had already installed the applicable May updates. Confirm the matching KB and resulting build. The Microsoft 2026-May CVRF supplies the following product-ID-to-update mapping. These are source-listed updates, not a claim that they are the newest available packages. Confirm supersedence, support entitlement and installation prerequisites before deployment.
| Product and servicing branch | Update | Source-listed fixed build |
|---|---|---|
| Microsoft SharePoint Enterprise Server 2016 | KB5002868 | 16.0.5552.1002 |
| Microsoft SharePoint Server 2019 | KB5002870 | 16.0.10417.20128 |
| Microsoft SharePoint Server Subscription Edition | KB5002863 | 16.0.19725.20280 |
Workaround Or Temporary Mitigation
No specific Microsoft workaround is established here. Review unnecessary Site Member access and external reachability while updating, but neither replaces the SharePoint security fix or investigation of suspected prior code execution.
Important boundary: A workaround, access restriction, or provider-side control may reduce risk while the update is prepared, but it does not necessarily remove vulnerable code or erase an earlier compromise. Install the vendor-approved update when one is available.
Investigation And Recovery
CISA flags known ransomware-campaign use. Microsoft did not mark exploitation at original publication, but CISA added the CVE to KEV on 2026-07-01; review site membership, IIS, SharePoint, and endpoint evidence for suspicious code execution.
When an attacker may have gained administrative, root, SYSTEM, identity, management-plane, or code-execution access, patching alone is not an eradication claim. Preserve evidence, scope affected accounts and downstream systems, rotate exposed credentials or certificates when justified, and rebuild from a trusted source when vendor or incident-response guidance requires it.
Notes
Exploitation Evidence
Vendor statement: Microsoft marked Exploited: No at original publication; CISA subsequently added the CVE to KEV on 2026-07-01.
CISA statement: CVE-2026-45659 was added to KEV on 2026-07-01. The ransomware field is Known, and the forensic-triage field is Yes. These are separate signals.
Validation And Boundaries
This notice does not prove that every product carrying the family name is affected, that exploitation is widespread, that a clean indicator search rules out compromise, or that a successful update restored trust. TechGeeks has not reproduced the exploit and does not replace the vendor advisory, asset inventory, vulnerability scanner, or incident-response process.
Related TechGeeks Resources
- TechGeeks Security Notice Center
- All Security Notices
- What to Do When a Device Hits CISA KEV
- Router CVE Exposure, Version, and Mitigation Checklist
- IoT Firmware Update and End-of-Support Checklist
- Live Protect and Runtime Vulnerability Shielding
References
Wrap-Up
Record whether CVE-2026-45659 applies to your environment. If it does, assign an owner, preserve the change and investigation evidence, complete the vendor action, and document the validated result.
Correction policy: If a primary source changes affected versions, remediation, exploitation status, or recovery guidance, TechGeeks will update this page and its verification date.
