dbcve.org
Dynamics 365 Business CentralApplication · Microsoft

CVE-2026-40417

HIGH · 7.8 CVSS v3.1 Published 2026-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Weak authentication in Dynamics Business Central allows an authorized attacker to elevate privileges locally.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a local privilege escalation vulnerability in Microsoft Dynamics Business Central stemming from weak authentication mechanisms. An attacker who already has authorized access to the system can exploit weak authentication to elevate their privileges to a higher permission level within the local environment.

MitigationApply Microsoft security updates for Dynamics Business Central when released. Review and enforce strong authentication policies, implement least-privilege user roles, and monitor for unusual privilege escalation activities.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Dynamics 365 Business CentralApplication
Affected:= 2024= 2025= 2026

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Dynamics Business Central version
    Check the installed version through Windows Programs and Features, or query the server via Get-NAVVersion or Business Central administration console. Look for version numbers 2024, 2025, or 2026 in the build information.
    Affected if The installed version matches 2024, 2025, or 2026 exactly.
  2. Verify the Server instance is running
    Open Business Central Administration Shell and run Get-NAVServerInstance to list all server instances. Confirm the ServerInstance is in Running state.
    Affected if A server instance exists and is running a vulnerable version.
  3. Check authentication method configuration
    Open Business Central Administration Shell and run Get-NAVServerConfiguration -ServerInstance <instance> to inspect authentication settings. Look for authentication methods like NavUserPassword, Azure AD, or Windows that may be improperly configured.
    Affected if The authentication method is set to NavUserPassword or another weak authentication protocol without additional MFA enforcement.
  4. Review user role assignments and permissions
    Open Business Central web client as an administrator, navigate to Users page, and examine the Security table and Role assignments. Check for users assigned to privileged roles like SUPER or ADMINISTRATOR.
    Affected if Users with elevated permissions exist in the system, creating potential escalation targets.
  5. Audit credential and credential store settings
    Check the credential type configured for the server instance via Get-NAVServerConfiguration. Inspect Windows Credential Manager or any external credential stores for stored credentials used by Business Central services.
    Affected if Stored credentials are used without proper protection or if credential encryption is weak.

A user is affected if Microsoft Dynamics Business Central version 2024, 2025, or 2026 is installed with weak or improperly configured authentication methods and elevated user roles are present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply Microsoft security updates for Dynamics Business Central when released. Review and enforce strong authentication policies, implement least-privilege user roles, and monitor for unusual privilege escalation activities.

Fix this in Dynamics 365 Business Central Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,330
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40417 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40417 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data