D365 F&O MCP Server is a Model Context Protocol server for querying Dynamics 365 Finance & Operations X++ code and metadata. Prior to version 1.11.0, the officially documented Azure one-click deployment uses infrastructure/azuredeploy.json and infrastructure/main.bicep to default the apiKey parameter to an empty string and pass it to the App Service API_KEY setting. With API_KEY unset or empty, src/middleware/apiKeyAuth.ts passes requests through without authentication, while src/index.ts binds the HTTP listener to 0.0.0.0 by default. If the deployer leaves the optional key blank and does not add separate network restrictions or upstream authentication, the resulting public App Service allows unauthenticated JSON-RPC tools/call requests to /mcp. The deployment's MCP_SERVER_MODE=read-only setting does not prevent anonymous access to read/search tools, including search, get_object_info, batch_get_info, extension_info, security_info, find_references, and find_event_handlers, exposing indexed proprietary X++ source snippets and metadata. Exposed information can include business logic, extension and event-handler wiring, security-role and privilege structure, and labels originally indexed from PackagesLocalDirectory. Deployments protected by a configured API key, effective upstream authentication, or network restrictions preventing attacker access are outside this unauthenticated exposure scenario. This issue is fixed in version 1.11.0.
CVE-2026-114123
“—” beside the score: it is equal to the CVSS score beside it.
This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (36th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-107365 (ENISA EUVD)Source: ENISA EUVD
- High severity, but no confirmed exploitation yet
A fix is available — apply it.
- CVSS v3
- 7.5
- EG Score
- 7.5HIGHmedium confidence
- EG Risk
- 49EG Risk 49/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity75% × 45%Impact severity (EG Severity): CVSS 7.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation0.4% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability100% × 15%CISA's SSVC Automatable value: yes (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.4%
- EPSS %ILE
- 36th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (7.5): severity, escalated by confirmed exploitation. This CVE's 7.5 is its impact severity (EG Severity), not escalated.
- EG Severity
- 7.5 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
October 21, 2026
Last Modified
October 30, 2026
Advisory Details (4)
Auto-updated Oct 21, 2026Official Azure one-click deployment ships with authentication disabled by default, exposing proprietary X++ source over the public internet · Advisory · dynamics365ninja/d365fo-mcp-server · GitHub
https://github.com/dynamics365ninja/d365fo-mcp-server/security/advisories/GHSA-8764-fh3m-wf7gv1.11.0
Patch available: dynamics365ninja/d365fo-mcp-server v1.11.0
https://github.com/dynamics365ninja/d365fo-mcp-server/releases/tag/v1.11.0commit e70bd051f817 (dynamics365ninja/d365fo-mcp-server)
Patch available: dynamics365ninja/d365fo-mcp-server v1.11.0 (contains commit e70bd051f817)
https://github.com/dynamics365ninja/d365fo-mcp-server/commit/e70bd051f817ebb652d664b10a944fe2c5495de2commit 384394a81e1c (dynamics365ninja/d365fo-mcp-server)
Patch available: dynamics365ninja/d365fo-mcp-server v1.11.0 (contains commit 384394a81e1c)
https://github.com/dynamics365ninja/d365fo-mcp-server/commit/384394a81e1c6c1e0149586203395240a38fc818Weakness Classification(2)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 20× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.
- 2026-11-02 16:44 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-30 20:26 UTCEG score recompute
- 2026-10-30 19:50 UTCEG score recompute
- 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-30 01:36 UTCEG score recompute
- 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 36th percentile
- 2026-10-25 14:50 UTCEG score recompute
- 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-22 17:47 UTCEG score recompute
- 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.4% · 35th percentile
- 2026-10-21 17:27 UTCEG score recompute
- 2026-10-21 17:08 UTCEG score recomputeFirst assessed: 7.5 HIGH
- 2026-10-21 17:05 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-306 · CWE-1188
Frequently asked(5)
What is CVE-2026-114123?
When was the CVE record for CVE-2026-114123 published?
Is CVE-2026-114123 actively exploited?
What is the CVSS score of CVE-2026-114123?
How do I remediate CVE-2026-114123?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-114123
Is Your Infrastructure Affected by CVE-2026-114123?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.