CVE-2025-53770 remediation guide
Microsoft Microsoft SharePoint Enterprise Server 2016, Microsoft SharePoint Server 2019, Microsoft SharePoint Server Subscription Edition
Deserialization of untrusted data in on-premises Microsoft SharePoint Server allows an unauthorized attacker to execute code over a network. Microsoft is aware that an exploit for CVE-2025-53770 exists in the wild. Microsoft is preparing and fully testing a comprehensive update to address this vulnerability. In the meantime, please make sure that the mitigation provided in this CVE documentation is in place so that you are protected from exploitation.
Identify the affected asset
Confirm whether Microsoft Microsoft SharePoint Enterprise Server 2016, Microsoft SharePoint Server 2019, Microsoft SharePoint Server Subscription Edition is installed, record the deployed version and installation path, and identify exposed interfaces.
- Record the product name, package or appliance identifier, and installed version.
- Identify internet-facing, administrative, API, and internal access paths.
- Preserve the pre-change configuration and relevant service logs.
Validate the affected-version match
Compare the deployed version with the affected range: >= 16.0.0 < 16.0.5513.1001, >= 16.0.0 < 16.0.10417.20037, >= 16.0.0 < 16.0.18526.20508, < 16.0.18526.20508, 2016, 2019. Treat incomplete inventory results as unresolved.
Prioritize with independent signals
CISA has listed this vulnerability in the Known Exploited Vulnerabilities catalog. Combine this signal with asset criticality, exposure, compensating controls, and business impact.
Apply supported remediation
Disconnect public-facing versions of SharePoint Server that have reached their end-of-life (EOL) or end-of-service (EOS) to include SharePoint Server 2013 and earlier versions. For supported versions, please follow the mitigations according to CISA (URL listed below in Notes) and vendor instructions (URL listed below in Notes). Adhere to the applicable BOD 22-01 guidance for cloud services or discontinue use of the product if mitigations are not available.
Verify the result
Confirm the resulting version, service health, authentication and access paths, monitoring coverage, and relevant security logs.
- Confirm the expected version and package state.
- Run a functional health check for critical service paths.
- Review authentication, error, application, and security monitoring logs.
- Reassess exposure if the supported fix cannot be applied.
Operational boundary
This page does not replace the vendor advisory, support contract, change-management process, or recovery plan. Do not infer that an asset is unaffected from an incomplete inventory query or a missing fixed-version field.