Patch tracker / CVE reference / CVE-2026-48560
CVE-2026-48560
CVE-2026-48560 is a medium severity Microsoft vulnerability with a CVSS score of 5.4. Its EPSS score puts the probability of exploitation in the next 30 days at 35%. 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
Not in the CISA KEV catalog. EPSS exploit probability 35%. CVSS 5.4 (Medium).
This CVE is among the lower half of tracked Microsoft CVEs by EPSS exploit probability.
Continuing the SharePoint spoofing cluster, this flaw covers 2016, 2019, and Subscription Edition at CVSS 8.8 and 2 percent EPSS. Portal spoofing undermines the trust users place in shared sites, which is the foothold for credential-harvesting lures. The volume of these flaws makes a single comprehensive SharePoint update the efficient response.
Do this: Deploy the SharePoint server update fleet-wide to close this spoofing flaw with the others in the batch.
AI-generated from public data, 2026-07-07. Verify against the vendor advisory before acting.
Senserva AI Opinion and rich prompt for CVE-2026-48560
Copy this prompt into Claude, ChatGPT, or Copilot. The facts are included, sourced from this page.
Official patch(es) for CVE-2026-48560
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 KB5002873, KB5002874, KB5002880 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-48560. 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.
Scope and sources
- Affected products
- Fixed by the same updates
- Authoritative references
Want every Microsoft CVE and the patches that fix it, ranked by real-world risk? See the Microsoft Patch Tracker.