CVE-2026-123809: medium-severity vulnerability in dynatrace-oss dynatrace-mcp
Dynatrace MCP Server: Workflow template injection via create_workflow_for_notification
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
13Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 4.2epss 0.2%
Dynatrace MCP Server is an MCP server for Dynatrace Observability. Prior to 2.0.0, the create_workflow_for_notification tool inserts the caller-controlled teamName, problemType, and channel values into a Dynatrace workflow without neutralizing Jinja2 expressions. A caller can place template expressions such as event() in those values, and the workflow engine evaluates them when the persistent workflow runs. When the workflow has a valid Slack connector, the resulting Slack action can disclose event or tenant metadata to an attacker-selected channel; the shipped placeholder connection does not deliver messages by itself. The workflow remains in the tenant after the MCP session and credentials are gone. The isPrivate option defaults to false, making the created workflow tenant-visible unless the caller changes it. Exploitation requires either an MCP prompt-injection path or an operator approving a prompt that displays the template fragment literally. This issue is fixed in version 2.0.0.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
Affected products
dynatrace-oss · dynatrace-mcpRelated CVEs — dynatrace-oss dynatrace-mcp
In the same product, most dangerous first.
CVE-2026-123810MEDIUMDynatrace MCP Server: DQL injection via parameters not documented as DQLEPSS 0.4%CVE-2026-123811HIGHDynatrace MCP Server: Unauthenticated HTTP MCP Tool Invocation in `@dynatrace-oss/dynatrace-mcp-server`EPSS 0.3%CVE-2026-123812LOWDynatrace MCP Server: create_dynatrace_notebook missing the human-approval gateEPSS 0.3%