CVE-2026-20963: SharePoint unauthenticated deserialization RCE
Tech GuruQuick Answer
Microsoft's corrected FAQ describes CVE-2026-20963 as unauthenticated network code injection and execution on SharePoint Server. The March 17 revision changed the FAQ and CVSS information, not the January update requirement. Inventory the on-premises farm, apply the applicable security update to every server and preserve IIS, SharePoint and endpoint evidence. CISA's March 18 KEV addition is later than Microsoft's original Exploited: No assessment.
Fix Or Immediate Action
What to do now: Install the newest applicable cumulative SharePoint security update across the entire farm and verify every server.
Evidence check: The vendor evidence and its limits are described below. CISA KEV catalog 2026.10.02 was checked October 2; catalog chronology is separate from vendor publication history and evidence of compromise in your deployment. No exploit or update test is claimed.
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: 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 |
|---|---|
| CVE | CVE-2026-20963 |
| TechGeeks response tier | P0 — confirm an exact match and act now |
| CISA KEV added | 2026-03-18 |
| Vendor severity | Important |
| 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 | No in the current CISA field; organizations should still investigate when exposure or evidence warrants it. |
| CWE | CWE-502 |
| Federal remediation date | 2026-03-21 — applies to covered federal agencies; other organizations should set a risk-based deadline. |
What Happened
Microsoft SharePoint Deserialization of Untrusted Data Vulnerability. Microsoft SharePoint contains a deserialization of untrusted data vulnerability that allows an unauthorized 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
The January CVRF maps SharePoint Enterprise Server 2016, SharePoint Server 2019 and Subscription Edition to separate fixes. Treat those as historical product/update rows, not a claim that each branch remains supported today or that SharePoint Online is affected.
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 across the entire farm and verify every server.
- 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
These January fixes remain the mapped remediation in the checked record. Microsoft calls its March 17 FAQ/CVSS correction informational; do not mistake that revision date for a different patch release. These rows come from the Microsoft CVRF checked October 2. Match the exact product and update type; confirm current support, supersedence and prerequisites before installation. A listed historical fix is not a recommendation to install an obsolete package.
| Product | Update and type | Fixed build / qualification |
|---|---|---|
| Microsoft SharePoint Enterprise Server 2016 | KB5002828 Security Update | 16.0.5535.1001 |
| Microsoft SharePoint Server 2019 | KB5002825 Security Update | 16.0.10417.20083 |
| Microsoft SharePoint Server Subscription Edition | KB5002822 Security Update | 16.0.19127.20442 |
Workaround Or Temporary Mitigation
No CVE-specific workaround is supplied by the checked Microsoft record. Reduce unnecessary farm exposure while deploying the update, but do not label network restrictions a correction to unsafe deserialization or evidence of eradication.
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
The flaw permits unauthenticated network remote code execution. Microsoft did not mark it exploited at original publication, but CISA added it to KEV on 2026-03-18; preserve IIS, SharePoint, authentication, and endpoint evidence.
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-03-18.
CISA statement: CVE-2026-20963 was added to KEV on 2026-03-18. The ransomware field is Unknown, and the forensic-triage field is No. 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-20963 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.
