Skip to content

AAK-MCP-DYNATRACE-CVE-2026-123810-001: Dynatrace MCP server below 2.1.1: tool arguments reach DQL queries and workflow templates unescaped

Severity
MEDIUM
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
DynatraceMcpDqlAndWorkflowInjection

What it detects

The Dynatrace MCP server (npm @dynatrace-oss/dynatrace-mcp-server, dynatrace-oss/dynatrace-mcp) builds DQL queries and Dynatrace workflows from its tools' arguments. Before 2.1.1 several read tools put caller values into DQL with no validation or escaping: entityNames in the entity search, timeframe in the problem, vulnerability, exception and Kubernetes event queries, and clusterId and kubernetesEntityId in the Kubernetes event filter. A value can close the string, add pipeline stages or comment out the rest of the query, and so escape the field, time-window and result limits of tools marked readOnlyHint, which a client may run without asking (CVE-2026-123810, CVSS 3.1 4.3, CWE-89, GHSA-pqh8-p93p-2rx7). Before 2.0.0 create_workflow_for_notification put teamName, problemType and channel into a workflow whose Jinja2 expressions Dynatrace evaluates each time it runs, tenant-visible unless isPrivate was set and kept after the session ends (CVE-2026-123809, CVSS 3.1 4.2, CWE-1336, GHSA-xrmj-5g4g-8987). Before 1.8.7 create_dynatrace_notebook wrote tenant-visible notebooks, which can hold DQL that other users run, without the operator approval the other write tools ask for (CVE-2026-123812, CVSS 3.1 3.7, CWE-862, GHSA-pc2w-4mq8-32qw). The DQL injection reads no data beyond what the configured token's own execute_dql can. Checked in the published npm packages: 0.1.0, the first release, already puts clusterId into a DQL string, 2.1.0 still interpolates every value the advisory lists, and 2.1.1 validates timeframe and escapes the strings; the workflow tool ships from 0.1.0 until 2.0.0 removes it; the notebook tool first ships in 1.2.0, and 1.8.7 adds the approval prompt.

How to fix

Upgrade @dynatrace-oss/dynatrace-mcp-server to 2.1.1 or later and pin it; 2.1.2 is the final release and the repository is archived. Do not let a client run the server's tools without asking on the strength of readOnlyHint, and delete any [MCP POC] Notify team workflow an earlier release left in the tenant.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-DYNATRACE-CVE-2026-123810-001

Limitations

Reports @dynatrace-oss/dynatrace-mcp-server below 2.1.1 where a package.json, lockfile or MCP config states the version, reporting a range that admits an affected version. Docker's MCP catalog image mcp/dynatrace-mcp-server is not read: it publishes only latest (a 2.1.0 build on 2026-11-11, whose server bundle is byte-identical to npm's 2.1.0), and an untagged or latest reference does not say which build a project pulled, so it would still be reported after a rebuild from a fixed release. Reported at MEDIUM throughout: 2.0.0 to 2.1.0 carry only CVE-2026-123810, releases before 1.2.0 have no notebook tool, and the LOW notebook gap of 1.2.0 to 1.8.6 is reported at MEDIUM. npm's latest was 2.1.2 on 2026-11-11 and states no version, so the README's @latest launch, an unversioned reference and a config that runs a global install by its executable name, mcp-server-dynatrace, are not reported. It reads the version, not which tools the client lets the model call or approves without asking. Releases from 0.5.0 below 2.0.0 also fire AAK-MCP-DYNATRACE-CVE-2026-123811-001. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-DYNATRACE-CVE-2026-123810-001.md: the page then shows that text, with the registry reference appended under it.