Vulnerabilities/Microsoft/CVE-2025-49706
CVE-2025-49706: Microsoft SharePoint Improper Authentication Vulnerability
CISA KEV entry · Last checked 15 Nov 2026, 13:39 UTC
Exploitation confirmedRansomware use knownFix: Unknown
Microsoft SharePoint contains an improper authentication vulnerability that allows an authorized attacker to perform spoofing over a network. Successfully exploitation could allow an attacker to view sensitive information and make some changes to disclosed information. This vulnerability could be chained with CVE-2025-49704. CVE-2025-53771 is a patch bypass for CVE-2025-49706, and the updates for CVE-2025-53771 include more robust protection than those for CVE-2025-49706.
Recommended action
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.
CISA due date 23 Jul 2025 · CWE-287
Am I affected?
| Product | Affected versions | Fixed in |
|---|---|---|
| Microsoft SharePoint Enterprise Server 2016 | 16.0.0 to before 16.0.5508.1000 | Unknown |
| Microsoft SharePoint Server 2019 | 16.0.0 to before 16.0.10417.20027 | Unknown |
| Microsoft SharePoint Server Subscription Edition | 16.0.0 to before 16.0.18526.20424 | Unknown |
No source states a fixed version. Check the vendor advisory below.
Before you patch
Restart
See vendor guidance.Known issues
Check release notes.Verification
Confirm installed version.Timeline
- 22 Jul 2025 · Added to CISA KEV
- 23 Jul 2025 · CISA due date
Sources checked
| CISA KEV | 15 Nov 2026, 13:39 UTC |
| CVE List v5 | 30 Oct 2026, 12:11 UTC |
| NVD | 15 Nov 2026, 13:39 UTC |
| FIRST EPSS | 15 Nov 2026, 13:39 UTC |
Data from CISA, MITRE, NVD and FIRST. Sources and licences.
Wrong affected version, fix or exploitation status? Report a correction. Include the vendor source if you have it.