Patch tracker / CVE reference / CVE-2026-26105

CVE-2026-26105

CVE-2026-26105 is a high severity Microsoft vulnerability with a CVSS score of 8.8. 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

High

8.8

CVSS

3.0%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability 3.0%. 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-26105

A spoofing vulnerability in on-premises SharePoint, covering SharePoint 2016, 2019, and Subscription Edition, rated High Severity at CVSS 8.8. Spoofing in SharePoint typically lets an attacker present forged content or identity inside an intranet users treat as inherently trustworthy, which makes it a credential-harvesting platform. EPSS is only 2 percent, so this is a scheduled-patching item rather than an emergency, but SharePoint's exploitation history argues against letting it age.

Do this: Include this fix in your next SharePoint maintenance window across 2016, 2019, and Subscription Edition farms rather than deferring it a cycle.

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

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

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-26105 (source: https://senserva.com/cve/CVE-2026-26105.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed twice a day (5 AM and 3 PM US Central)):
- CVE-2026-26105: High severity Microsoft vulnerability, CVSS 8.8
- EPSS 30-day exploitation probability: 3.0%
- Actively exploited (CISA KEV): no
- Fixed by: KB5002843, KB5002845, KB5002850
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.

Schedule normally

No exploitation observed: not in the CISA KEV catalog, EPSS 3%.

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

Do this now: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Official patch(es) for CVE-2026-26105

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5002843, KB5002845, KB5002850 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-26105. 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.

KB5002843 KB5002845 KB5002850

Scope and sources

Affected products

Fixed by the same updates

CVE-2026-26106 CVE-2026-26113 CVE-2026-26114

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.