Read the docs

DQL injection in Dynatrace MCP Server read capabilities

Priority MEDIUM 53CWE-89Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
Required
Attack complexity
Low
Impact type
SQL injection
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-89.

Summary

Dynatrace MCP Server before 2.1.1 interpolates caller-controlled values into DQL queries without sufficient validation or escaping. Crafted values in the entity name, timeframe, cluster and Kubernetes entity parameters of several read capabilities can close string literals, append pipeline stages, or comment out the rest of the query. An attacker who can call these tools can break the field selection, time-window and result-display limits of tools marked readOnlyHint, though the flaw grants no data access beyond the token's existing execute_dql capability. This is a SQL injection weakness (CWE-89) with a CVSS 3.1 base score of 4.3 and a public proof-of-concept rated by CISA SSVC.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

Description from the CNA

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00229 13th percentileScored 2026-11-16
Fix Fixed dynatrace-mcp (dynatrace-oss): 2.1.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
Poc
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
dynatrace-ossdynatrace-mcpbefore 2.1.12.1.1Patch availableCNA
  • dynatrace-mcp Vendordynatrace-oss Affected before 2.1.1 Fixed in 2.1.1 Patch available CNA

Remediation

Update dynatrace-mcp to version 2.1.1, which fixes the issue. The sources list no vendor advisory identifier for this fix.

Written with Claude Haiku 5.5 from the sources below · 2026-11-10

  • Fix · CNA dynatrace-mcp (dynatrace-oss) Fixed in 2.1.1

Timeline

  1. 2026-11-09 Threatist record created from CVE-2026-123810
  2. 2026-11-10 CISA SSVC decision points changed
  3. 2026-11-10 Priority changed: LOW → MEDIUM

References

  • TI-2026-87369 Dynatrace MCP Server HTTP mode accepts unauthenticated tool calls CVSS 3.1HIGH 7.5
  • TI-2026-87370 Missing approval gate in Dynatrace MCP Server notebook creation tool CVSS 3.1LOW 3.7
  • TI-2026-87364 Template injection in Dynatrace MCP Server workflow creation CVSS 3.1MEDIUM 4.2

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences