Patch tracker / CVE reference / CVE-2026-40368

CVE-2026-40368

CVE-2026-40368 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

9.1%

EPSS, 30 days

High

Severity

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

One of several SharePoint Server remote code execution flaws disclosed in this period across 2016, 2019, and Subscription Edition, High Severity at CVSS 8.8 with EPSS at 3 percent. Repeated RCE findings in the same product line indicate sustained researcher attention on SharePoint's server-side processing, and history shows the gap between disclosure and mass exploitation there can be short. On-premises farms lack the automatic patching their cloud counterpart gets.

Do this: Fold this into a single SharePoint patching pass with the other current SharePoint CVEs rather than triaging each individually.

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

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

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

Schedule normally

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

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: Deploy with your normal update cycle. This page refreshes daily; the verdict changes the day the data does.

Official patch(es) for CVE-2026-40368

Moderate priority: schedule it in your normal patch cycle. 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-40368. 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-40365 CVE-2026-40367 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.