Patch tracker / CVE reference / CVE-2026-40365

CVE-2026-40365

CVE-2026-40365 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 76%. 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 v3

76%

EPSS, 30 days

High

Severity

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

This CVE is among the top 25% of tracked Microsoft CVEs by EPSS exploit probability.

Senserva AI Opinion for CVE-2026-40365

Yet another High Severity (CVSS 8.8) SharePoint Server Remote Code Execution vulnerability in the 2016, 2019, and Subscription Edition line, with EPSS at 3%. At this point the individual bug matters less than the aggregate exposure: multiple concurrent RCE paths into the same farms mean a single missed update leaves several doors open at once. SharePoint's ransomware history makes that an expensive oversight.

Do this: Confirm patch compliance across all SharePoint servers with an actual version check on each farm member, not just the deployment tool's report.

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

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

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-40365 (source: https://senserva.com/cve/CVE-2026-40365.html, data from MSRC, CISA KEV, FIRST.org EPSS, NVD, refreshed once a day (5 AM US Central)):
- CVE-2026-40365: High severity Microsoft vulnerability, CVSS 8.8
- EPSS 30-day exploitation probability: 76%
- Actively exploited (CISA KEV): no
- Fixed by: KB5002863, KB5002868, KB5002870
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 76%).

Fixed by KB5002863 and 2 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-40365

High priority: EPSS puts the odds of near-term exploitation high. In Intune or Defender, confirm whether the fixing updates KB5002863, KB5002868, KB5002870 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-40365. 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.

KB5002863 KB5002868 KB5002870

Scope and sources

Affected products

Fixed by the same updates

CVE-2026-45659 CVE-2026-33110 CVE-2026-33112 CVE-2026-35439 CVE-2026-40357 CVE-2026-40367 CVE-2026-40368 CVE-2026-47294

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.