Authenticated code execution via untrusted deserialization
Published Nov 11, 2025 · Updated Feb 26, 2026
Untrusted deserialization in Microsoft SharePoint Server before the listed November 2025 builds allows remote authenticated users to execute code. Microsoft has not published the affected component, deserialization entry point, serialized type, or validation failure that accepts attacker-controlled data. Exploitation requires low-privileged authentication and user interaction; success runs attacker-supplied code in the SharePoint server context.
Summary
What happened
Untrusted deserialization in Microsoft SharePoint Server before the listed November 2025 builds allows remote authenticated users to execute code. Microsoft has not published the affected component, deserialization entry point, serialized type, or validation failure that accepts attacker-controlled data. Exploitation requires low-privileged authentication and user interaction; success runs attacker-supplied code in the SharePoint server context.
The record
- CVE
- CVE-2025-62204
- Published
- Nov 11, 2025
- Updated
- Feb 26, 2026
- Vendor
- Microsoft
- Product
- Microsoft SharePoint Enterprise Server 2016
- Classifications
- CWE-502
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 11, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=16.0.0 <16.0.5526.1001
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo