Patch tracker / CVE reference / CVE-2026-40417

CVE-2026-40417

CVE-2026-40417 is a high severity Microsoft vulnerability with a CVSS score of 7.8. Microsoft has shipped the fix: deploy one of the 4 updates below from the Microsoft Update Catalog, and see where this CVE sits against the rest on the patch tracker.

Risk summary

High

7.8

CVSS v3

<1%

EPSS, 30 days

High

Severity

Not in the CISA KEV catalog. EPSS exploit probability <1%. CVSS 7.8 (High).

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

Senserva AI Opinion for CVE-2026-40417

Business applications take a rare turn here: Microsoft Dynamics 365 Business Central, across the 2025 Release Waves 1 and 2 and the 2026 Release Wave 1, has a High (CVSS 7.8) elevation of privilege flaw. EPSS shows 0 percent exploit probability, so risk is modest, but Business Central holds finance and ERP data where privilege boundaries between roles genuinely matter. Organizations self-hosting Business Central need to act, while cloud tenants should confirm Microsoft has applied the fix.

Do this: Update self-hosted Business Central instances on the affected release waves and verify role-based permissions behave as expected afterward.

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

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

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

Fixed by KB5086068 and 3 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-40417

Moderate priority: schedule it in your normal patch cycle. In Intune or Defender, confirm whether the fixing updates KB5086068, KB5086069, KB5086070, KB5093780 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-40417. 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.

KB5086068 KB5086069 KB5086070 KB5093780

Scope and sources

Affected products

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.