CVE-2026-58644: SharePoint unauthenticated deserialization RCE
Tech GuruQuick Answer
Microsoft records exploitation of CVE-2026-58644, a SharePoint deserialization code-execution flaw. Its description and CVSS vector indicate no authentication, but the FAQ requires Site Owner access; that conflict remains unresolved. Apply the CVE-specific edition mapping below to every applicable farm server and preserve incident evidence. Do not substitute the fixes for another SharePoint notice or treat the narrower FAQ as proof that exposure is limited.
Fix Or Immediate Action
What to do now: Install the newest applicable cumulative SharePoint security update on every farm server and verify the installed builds.
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.
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: Attacker-controlled serialized data can lead to remote code execution. Microsoft gives inconsistent authentication prerequisites: no privileges in the description/vector, but Site Owner in the FAQ.
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 |
|---|---|
| CVE | CVE-2026-58644 |
| TechGeeks response tier | P0 — confirm an exact match and act now |
| CISA KEV added | 2026-07-16 |
| Vendor severity | Critical |
| CVSS | 9.8 (CVSS v3.1 base) |
| Ransomware field | Unknown — this is not the same as No; CISA has not marked the field Known. |
| Forensic-triage field | Yes — CISA's record calls for forensic triage. |
| CWE | CWE-502 |
| Federal remediation date | 2026-07-19 — applies to covered federal agencies; other organizations should set a risk-based deadline. |
What Happened
CISA describes CVE-2026-58644 as unauthorized network code execution through SharePoint deserialization. Microsoft's description and CVSS vector agree with that scope, but its FAQ requires Site Owner access. That prerequisite conflict remains unresolved. The KEV listing supports reported exploitation, not its prevalence or compromise of any particular farm.
Affected Scope
On-premises SharePoint Server 2016, SharePoint Server 2019, and SharePoint Server Subscription Edition where listed by Microsoft; exact farm-server applicability is controlled by the live MSRC table.
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 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 on every farm server and verify the installed builds.
- 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
Select this CVE's fix by SharePoint edition, then check supersedence; do not borrow a build from a different SharePoint vulnerability. The Microsoft 2026-Jul 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 | KB5002880 | 16.0.5556.1005 |
| Microsoft SharePoint Server 2019 | KB5002874 | 16.0.10417.20153 |
| Microsoft SharePoint Server Subscription Edition | KB5002873 | 16.0.19725.20384 |
Workaround Or Temporary Mitigation
No specific Microsoft workaround is established here. Reduce unnecessary external reachability while updating the farm, but do not treat that reduction as remediation or as a resolution of the conflicting authentication prerequisites.
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
Microsoft and CISA report exploitation. The CVRF's no-authentication description and Site Owner FAQ conflict; preserve IIS, SharePoint, authentication and endpoint evidence without limiting investigation to either prerequisite interpretation. Treat suspicious activity as an incident.
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: Yes at original publication.
CISA statement: CVE-2026-58644 was added to KEV on 2026-07-16. The ransomware field is Unknown, 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-58644 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.
