CVE-2025-59237: Microsoft SharePoint Enterprise Server 2016 · Deserialization of Untrusted Data
Affects Microsoft SharePoint Enterprise Server 2016Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 2.4% chance of exploitation in 30 days – higher than 84% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H/E:U/RL:O/RC:CExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Microsoft SharePoint Enterprise Server 2016 | Affected
| Fixed in– |
AI-suggested
- Apply patches from Microsoft immediately once they become available to address CVE-2025-59237.
- Until a patch is released, restrict network access to SharePoint servers to trusted internal networks and VPNs only.
- Implement strict access controls and least privilege principles for SharePoint users and services to limit potential attacker capabilities.
- Monitor network traffic and SharePoint logs for unusual deserialization activity or anomalous requests that could indicate exploitation attempts.
- Use application-layer firewalls or web application firewalls (WAFs) with custom rules to detect and block suspicious serialized payloads.
- Conduct regular security assessments and penetration testing focusing on deserialization vulnerabilities.
- Educate administrators and security teams about the risks of deserialization attacks and ensure incident response plans include this threat.
- Consider isolating SharePoint servers in segmented network zones to reduce lateral movement opportunities.
- Review and harden SharePoint configurations to minimize attack surface, disabling unnecessary features that process serialized data.
- Maintain up-to-date backups and test restoration procedures to recover quickly in case of compromise.
Description
Deserialization of untrusted data in Microsoft Office SharePoint allows an authorized attacker to execute code over a network.