Secuno
ENNL
Book demo

CVE-2026-40371

Microsoft Dynamics 365 vulnerability

8.8 HIGHEPSS 0.78%
  1. Published9 Jun 2026

Description

Improper handling of insufficient permissions or privileges in Microsoft Dynamics 365 (on-premises) allows an authorized attacker to elevate privileges over a network.

CVSS 3.1 breakdown

Attack vectorNetwork
Attack complexityLow
Privileges requiredLow
User interactionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected products

Microsoft Dynamics 365≥ 9.1 < 9.1.45.11

Remediation

Fixed in
Microsoft Dynamics 365≥ 9.1.45.11

References

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

CVE-2026-794038.4
An issue in Kilo Code before v7.4.1 allows a local attacker to execute arbitrary code…
CVE-2026-595678.8
Multiple vulnerabilities on affected versions of Zscaler Client Connector allow local…
CVE-2026-188608.7
Velociraptor allows multi-tenant deployments named "Orgs". By default Velociraptor,…
CVE-2026-240968.8
Insufficient permission validation on multiple REST API Quick Setup endpoints in…
CVE-2026-00478.4
In dumpBitmapsProto of ActivityManagerService.java, there is a possible way for an app…
CVE-2026-278099.1
psd-tools is a Python package for working with Adobe Photoshop PSD files. Prior to…

Frequently asked

Is CVE-2026-40371 being actively exploited?

CVE-2026-40371 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.78%.

How severe is CVE-2026-40371?

CVE-2026-40371 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 0.78% probability of exploitation.

Which products are affected by CVE-2026-40371?

Affected products include Microsoft Dynamics 365.

How do I fix CVE-2026-40371?

Upgrade affected software to a fixed version, for example Microsoft Dynamics 365 9.1.45.11 or later, then confirm no affected versions remain in your inventory.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-40371 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation worksBook a demo

Get Patch this first every Monday

Five vulnerabilities that matter this week, ranked on real exploitation. Plain language, one email, no spam.

You can unsubscribe with one click from every issue. We handle your details as described in our privacy policy.

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.