Dynatrace MCP Server: DQL injection via parameters not documented as DQL
- Exploited
- No known exploitation
- Fix
- Fixed in 2.1.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.1.1.
- 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? →
- 11/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 DQL injection flaw in several read tools where caller-supplied values such as entity names, timeframes, and cluster IDs are inserted into queries without proper validation. An attacker can reach it remotely over the network without logging in, but it requires a user to take an action, and the result is limited to bypassing field, time-window, and result-display restrictions on tools that are meant to be auto-approved, since it grants no data beyond what the configured token already allows.
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 2.1.1, several read capabilities interpolate caller-controlled values into DQL without sufficient validation or escaping. The src/capabilities/find-monitored-entity-by-name.ts capability embeds entityNames in string searches, src/capabilities/list-problems.ts, src/capabilities/list-vulnerabilities.ts, and src/capabilities/list-exceptions.ts embed timeframe values, and src/capabilities/get-events-for-cluster.ts embeds timeframe, clusterId, and kubernetesEntityId. Crafted values can close string literals, append pipeline stages, or comment out the remaining intended query, allowing callers to bypass field selection, time-window, and result-display limits in tools marked readOnlyHint. The issue does not grant data access beyond the configured token's existing execute_dql capability, but it breaks the narrower auto-approved tool contract. This issue is fixed in version 2.1.1.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity4.3/10CVSS 4.3
- 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: 2.1.1.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- dynatrace-oss dynatrace-mcp
fixed in 2.1.1
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-123810
Is CVE-2026-123810 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-123810?
dynatrace-mcp: before 2.1.1.Source: cve.now feed data
How do I fix CVE-2026-123810?
Upgrade to a fixed version: 2.1.1.Source: cve.now feed data