CVE-2026-40375: Microsoft Dynamics Business Central Information Disclosure Vulnerability
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.84% (FIRST EPSS); higher than 57.5% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: Microsoft Dynamics 365 Business Central 2026 Release Wave 1 28.0.50938; Microsoft Dynamics 365 Business Central Release Wave 1 2025 26.0.50788; Microsoft Dynamics 365 Business Central Release Wave 2 2025 27.0.50789.
Low priority for now. Upgrade to Microsoft Dynamics 365 Business Central 2026 Release Wave 1 28.0.50938; Microsoft Dynamics 365 Business Central Release Wave 1 2025 26.0.50788; Microsoft Dynamics 365 Business Central Release Wave 2 2025 27.0.50789 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Missing authorization in Dynamics Business Central allows an authorized attacker to disclose information over a network.
- Published
- Aug 11, 2026
- Updated
- Oct 21, 2026
- EPSS
- 0.8% · 57th percentile
- CWE
- CWE-862
Report tools
Action score
26
Monitor
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · microsoft
- 6.5
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N/E:U/RL:O/RC:C
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| microsoft | dynamics 365 business central 2024 | cpe:2.3:a:microsoft:dynamics_365_business_central_2024 |
| microsoft | dynamics 365 business central 2025 | cpe:2.3:a:microsoft:dynamics_365_business_central_2025 |
| microsoft | dynamics 365 business central 2026 | cpe:2.3:a:microsoft:dynamics_365_business_central_2026 |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- microsoft dynamics 365 business central 202425.1.25900 and later
- microsoft dynamics 365 business central 202526.0 and later · before 26.0.50788
- microsoft dynamics 365 business central 202527.0 and later · before 27.0.50789
- microsoft dynamics 365 business central 202628.0 and later · before 28.0.50938
Versions reported by the vendor
Affected version ranges reported by the assigning authority (microsoft). Independent of NVD's CPE analysis and usually ahead of it.
Microsoft Microsoft Dynamics 365 Business Central 2024 Release Wave 2
- -affected
Microsoft Microsoft Dynamics 365 Business Central 2026 Release Wave 1
- 28.0 and later · before 28.0.50938affected
Microsoft Microsoft Dynamics 365 Business Central Release Wave 1 2025
- 26.0 and later · before 26.0.50788affected
Microsoft Microsoft Dynamics 365 Business Central Release Wave 2 2025
- 27.0 and later · before 27.0.50789affected
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Microsoft Dynamics 365 Business Central 2026 Release Wave 1 | 28.0.50938 · KB5100266 | Microsoft (MSRC) |
| Microsoft Dynamics 365 Business Central Release Wave 1 2025 | 26.0.50788 · KB5100263 | Microsoft (MSRC) |
| Microsoft Dynamics 365 Business Central Release Wave 2 2025 | 27.0.50789 · KB5100265 | Microsoft (MSRC) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-862 · Missing AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.