Dynatrace MCP Server: create_dynatrace_notebook missing the human-approval gate
- Exploited
- No known exploitation
- Fix
- Fixed in 1.8.7
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 1.8.7.
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 21/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Dynatrace MCP Server, an MCP server for Dynatrace Observability, has a flaw in its create_dynatrace_notebook tool that skips the human-approval step other write tools require. An attacker can remotely, without logging in, create tenant-visible notebooks containing malicious Markdown or DQL content, which tenant users may later run when they open the notebook.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Dynatrace MCP Server is an MCP server for Dynatrace Observability. Prior to 1.8.7, the create_dynatrace_notebook registration in src/index.ts performs a persistent document-write action without calling requestHumanApproval, although the project's other write tools use that gate to obtain operator consent. A caller can create tenant-visible notebooks containing attacker-controlled Markdown or DQL content, and tenant users may later execute embedded DQL when opening the notebook. The tool also lacks a destructiveHint annotation that would signal its side effects to MCP clients. This issue is fixed in version 1.8.7.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity3.7/10CVSS 3.7
- No patch0/5No signal
What would change the score
- Would score about 66 if added to CISA KEV
- Would score about 61 if CISA's SSVC rates exploitation active
- Would score about 26 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 1.8.7.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- dynatrace-oss dynatrace-mcp
fixed in 1.8.7
Evidence 3
- Advisory
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123812
Is CVE-2026-123812 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-123812?
dynatrace-mcp: before 1.8.7.Source: cve.now feed data
How do I fix CVE-2026-123812?
Upgrade to a fixed version: 1.8.7.Source: cve.now feed data