Template injection in Dynatrace MCP Server workflow creation
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- High
- Impact type
- Code execution
- Confidentiality · integrity · availability
- Low · Low · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-1336.
Summary
Dynatrace MCP Server before 2.0.0 does not neutralize Jinja2 template expressions in the teamName, problemType and channel values written into a Dynatrace workflow (CWE-1336), and the workflow engine evaluates them when the persistent workflow runs. With a valid Slack connector, the Slack action can disclose event or tenant metadata to an attacker-selected channel. The workflow stays in the tenant after the MCP session ends and is tenant-visible by default, because isPrivate defaults to false. Exploitation requires a prompt-injection path or an operator approving a prompt that shows the template fragment.
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.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.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- 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
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| dynatrace-oss | dynatrace-mcp | before 2.0.0 | 2.0.0 | Patch available | CNA |
- dynatrace-mcp Vendordynatrace-oss Affected before 2.0.0 Fixed in 2.0.0 Patch available CNA
Remediation
Upgrade dynatrace-mcp to version 2.0.0. The sources list no other fixed version for dynatrace-mcp.
Written with Claude Haiku 5.5 from the sources below · 2026-11-10
- Fix · CNA dynatrace-mcp (dynatrace-oss) Fixed in 2.0.0
Timeline
- 2026-11-09 Threatist record created from CVE-2026-123809
- 2026-11-10 CISA SSVC decision points changed
References
More dynatrace-oss vulnerabilities
- TI-2026-87369 Dynatrace MCP Server HTTP mode accepts unauthenticated tool calls CVSS 3.1HIGH 7.5
- TI-2026-87368 DQL injection in Dynatrace MCP Server read capabilities CVSS 3.1MEDIUM 4.3
- TI-2026-87370 Missing approval gate in Dynatrace MCP Server notebook creation tool CVSS 3.1LOW 3.7
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences