CVE-2026-123809 Dynatrace MCP Server: Workflow template injection via create_workflow_for_notification
- Exploited in the wild
- Not known
- Fix
- Available
What is CVE-2026-123809?
CVE-2026-123809 is a medium-severity vulnerability in dynatrace-oss dynatrace-mcp, published on 9 Nov 2026.
Official description
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.
Weakness: CWE-1336
Which versions are affected by CVE-2026-123809?
1 open source package ship an affected version, including @dynatrace-oss/dynatrace-mcp-server.
| Package | Affected | Fixed in |
|---|---|---|
@dynatrace-oss/dynatrace-mcp-server npm | All versions | 2.0.0 |
How do I fix CVE-2026-123809?
Upgrade @dynatrace-oss/dynatrace-mcp-server to 2.0.0 or later.
Is CVE-2026-123809 being exploited?
There is no known exploitation of CVE-2026-123809 in the wild and no public exploit code.
Sources
Also known as GHSA-xrmj-5g4g-8987.