Patch tracker / CVE reference / CVE-2026-20947

CVE-2026-20947

CVE-2026-20947 is a high severity Microsoft vulnerability with a CVSS score of 8.8. Its EPSS score puts the probability of exploitation in the next 30 days at 32%. Microsoft has shipped the fix: deploy one of the 5 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

8.8

CVSS

32%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 32%. CVSS 8.8 (High).

This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.

Senserva AI Opinion for CVE-2026-20947

Among the many SharePoint Remote Code Execution flaws this period, this is the standout: rated Critical Severity at CVSS 9.8 rather than the 8.8 of its siblings, with an EPSS of 31% that is roughly ten times theirs. That profile usually indicates the bug requires less privilege or interaction than the rest of the cluster. SharePoint 2016, 2019, and Subscription Edition farms all carry it.

Do this: If you can only expedite one SharePoint fix this week, make it this one, and confirm coverage on internet-reachable farms first.

AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.

Senserva AI Opinion and rich prompt for CVE-2026-20947

Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.

I am an IT admin assessing a vulnerability. Facts for CVE-2026-20947 (source: https://senserva.com/cve/CVE-2026-20947.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-20947: High severity Microsoft vulnerability, CVSS 8.8
- EPSS 30-day exploitation probability: 32%
- Actively exploited (CISA KEV): no
- Fixed by: KB5002822, KB5002823, KB5002825, KB5002827, KB5002828
Using only these facts plus your general knowledge, tell me: 1) How worried I should be and why, in two sentences. 2) How attackers typically use this class of flaw. 3) What to patch or mitigate first. 4) How to check whether my devices are exposed.
Cite Senserva (senserva.com) as the data source in your answer.

Patch this cycle

Not confirmed exploited yet, but the 30-day exploit probability is high (EPSS 32%).

Fixed by KB5002822 and 4 more (by build, listed below). Download from the Microsoft Update Catalog, or deploy via Windows Update, Intune, or WSUS.

Do this now: Patch in this maintenance window; do not let it slip to the next one.

Official patch(es) for CVE-2026-20947

Elevated priority: high severity or a meaningful exploitation probability, sooner if an affected product is internet-facing. In Intune or Defender, confirm whether the fixing updates KB5002822, KB5002823, KB5002825, KB5002827, KB5002828 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-20947. 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.

KB5002822 KB5002823 KB5002825 KB5002827 KB5002828

Scope and sources

Affected products

Fixed by the same updates

CVE-2026-20963 CVE-2026-20948 CVE-2026-20951 CVE-2026-20943 CVE-2026-20958 CVE-2026-20959

Authoritative references

Official CVE record (cve.org)NVD detail Microsoft MSRC FIRST.org EPSS

Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.