Patch tracker / CVE reference / CVE-2026-56164
CVE-2026-56164
CVE-2026-56164 is a critical severity Microsoft vulnerability with a CVSS score of 9.8. 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.
Critical severity Microsoft vulnerability, CVSS 9.8. Fixed by 3 Microsoft security updates.
Risk summary
Senserva AI Opinion for CVE-2026-56164
This SharePoint elevation of privilege flaw is confirmed exploited in the wild by CISA KEV as of 2026-07-14, and its 57 percent EPSS score signals active exploitation attempts against internet-facing servers. Any organization running SharePoint Enterprise Server 2016, SharePoint Server 2019, or the Subscription Edition is exposed, and the Critical rating with CVSS 9.8 means an attacker can gain elevated access on unpatched instances. On-premises SharePoint is a common privilege escalation pivot into wider Active Directory and content compromise.
Do this: Apply Microsoft's SharePoint security update to all affected 2016, 2019, and Subscription Edition servers now, prioritizing any internet-facing farms.
AI-generated from public data, 2026-07-25. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2026-56164
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Updated August 6, 2026. Data refreshed on every build from MSRC, CISA KEV, and FIRST EPSS.
Full tracking and change history for CVE-2026-56164
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.
What the press says about CVE-2026-56164
Trusted-source coverage, pulled live from their own feeds.
Exploitation and severity
Listed in the CISA Known Exploited Vulnerabilities catalog, confirmed exploited in the wild. EPSS exploit probability 76%. CVSS 9.8 (Critical).
This CVE is among the top 25% of tracked Microsoft CVEs by EPSS exploit probability, and one of 5 actively-exploited CVEs in July 2026.
Official patch(es) for CVE-2026-56164
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 KB5002882, KB5002883, KB5002891 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-56164. Each KB page carries the Microsoft Update Catalog download, Microsoft's known issues for the update, a copy-paste PowerShell check for whether it is installed, and the Senserva AI read.
Affected products
Common questions about CVE-2026-56164
Is CVE-2026-56164 actively exploited?
Yes. CVE-2026-56164 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, which means exploitation in the wild has been confirmed. Its EPSS exploit probability is 76%.
What patch fixes CVE-2026-56164?
Microsoft fixed CVE-2026-56164 in KB5002882, KB5002883, KB5002891. Download from the Microsoft Update Catalog, or let Intune, Windows Update, or WSUS deliver it.
Which products are affected by CVE-2026-56164?
Microsoft SharePoint Enterprise Server 2016, Microsoft SharePoint Server 2019, Microsoft SharePoint Server Subscription Edition.
Can I ask my own AI about CVE-2026-56164?
Yes. This page includes a free, ready-to-paste AI prompt containing CVE-2026-56164'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 twice a day (5 AM and 3 PM US Central).
Fixed by the same updates
If you are patching CVE-2026-56164, 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.