Patch tracker / CVE reference / CVE-2026-32201
CVE-2026-32201
Medium severity Microsoft vulnerability, CVSS 6.5. Fixed by 3 Microsoft security updates.
On this page, all about CVE-2026-32201: the Senserva AI read, whether it is exploited, the official patches, its change history, and the questions admins ask. Find every machine missing this see which of your devices still have this one, plus your complete patch state and all 650+ security checks with full reports, free: start your One Free Unlimited Audit. All you do is register.
CVE-2026-32201 is a medium severity Microsoft vulnerability with a CVSS score of 6.5. It is in the CISA Known Exploited Vulnerabilities catalog: attackers are using it in the wild, which makes it a fix-first item. Microsoft has shipped the fix: deploy one of the 3 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.
Risk summary
Senserva AI Opinion for CVE-2026-32201
Do not let the Medium Severity rating (CVSS 6.5) fool you: this SharePoint Server spoofing flaw was added to the CISA KEV catalog on April 14, 2026, meaning attackers are already using it against on-premises farms. It affects SharePoint Enterprise Server 2016, Server 2019, and Subscription Edition, and spoofing bugs on SharePoint are a common first step that gets chained into deeper compromise of the farm. The 25% EPSS score confirms exploitation interest is well above the norm for a Medium-rated issue.
Do this: Patch all on-premises SharePoint 2016, 2019, and Subscription Edition servers today and review recent authentication logs on those farms for anomalies.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2026-32201
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Full tracking and change history for CVE-2026-32201
Published and last-revised dates are authoritative, from Microsoft MSRC (or the CISA KEV date-added). Senserva additionally records day-to-day changes from 2026-07-07, refreshed several times a day; the change count reflects that forward-only tracking.
Exploitation and severity
Listed in the CISA Known Exploited Vulnerabilities catalog, confirmed exploited in the wild. EPSS exploit probability 25%. CVSS 6.5 (Medium).
This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability, and one of 2 actively-exploited CVEs in April 2026.
Official patch(es) for CVE-2026-32201
Treat as urgent: it is being exploited in the wild (CISA KEV), so patch ahead of items that are not. In Intune or Defender, confirm whether the fixing updates KB5002853, KB5002854, KB5002861 are installed across the affected products. Senserva does this automatically across your tenant and flags every missing patch.
Apply the Microsoft security updates below to fix CVE-2026-32201. Each KB page links to the Microsoft Update Catalog download for every affected product.
Affected products
Common questions about CVE-2026-32201
Is CVE-2026-32201 actively exploited?
Yes. CVE-2026-32201 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, which means exploitation in the wild has been confirmed. Its EPSS exploit probability is 25%.
What patch fixes CVE-2026-32201?
Microsoft fixed CVE-2026-32201 in KB5002853, KB5002854, KB5002861. Download from the Microsoft Update Catalog, or let Intune, Windows Update, or WSUS deliver it.
Which products are affected by CVE-2026-32201?
Microsoft SharePoint Enterprise Server 2016, Microsoft SharePoint Server 2019, Microsoft SharePoint Server Subscription Edition.
Can I ask my own AI about CVE-2026-32201?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-32201's key facts: severity, CVSS, EPSS exploit probability, CISA KEV status, and the fixing KB. Copy it into Claude, ChatGPT, or Copilot for a triage plan; the data is refreshed three times a day (5 AM, 12:30 PM, and 7 PM US Central).
Fixed by the same updates
If you are patching CVE-2026-32201, the same updates also fix these:
Authoritative references
Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.
