AI Stack Alert Medium CVE-2026-123809 For AI Eng, AppSec, SOC / IR, CISO AI-assisted
CVE-2026-123809: Dynatrace MCP Server template injection in create_workflow_for_notification
Dynatrace MCP Server versions before 2.0.0 insert caller-supplied teamName, problemType, and channel values into Dynatrace workflows without neutralizing Jinja2 expressions. The workflow engine evaluates those expressions when the persistent workflow runs, and a valid Slack connector can then disclose event or tenant metadata to an attacker-selected channel. The fix is in version 2.0.0.
Why it matters
Organizations running affected versions may have persistent, tenant-visible workflows that outlive the MCP session and can leak event or tenant metadata through a configured Slack connector. The source states exploitation requires either an MCP prompt-injection path or an operator approving a prompt that shows the template fragment literally.
Do this
- Upgrade the Dynatrace MCP Server to version 2.0.0 or later.
- Audit Dynatrace workflows created through create_workflow_for_notification, and review their teamName, problemType, and channel fields for Jinja2 template expressions.
- Check whether those workflows use a live Slack connector, and confirm the destination channels are expected.
- Review workflow visibility: the isPrivate option defaults to false, so confirm which workflows are tenant-visible and set isPrivate where appropriate.
- Require operators to review the full text of MCP-generated prompts before approving tool actions that create workflows.
Exploit Clock
No signals yet
- No exploitation signals yet
Signals
- NoCISA KEV
- 4.2CVSS
- NoPublic PoC
- 27/100Priority
- 80%Confidence
Evidence
“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.”
“The isPrivate option defaults to false, making the created workflow tenant-visible unless the caller changes it.”
“The workflow remains in the tenant after the MCP session and credentials are gone.”
“Exploitation requires either an MCP prompt-injection path or an operator approving a prompt that displays the template fragment literally.”
Sources
Affected / related
Dynatrace MCP Server, Dynatrace, Dynatrace MCP Server, Jinja2 template injection
Published 2026-11-09 22:18 UTC · updated 2026-11-10 03:06 UTC · AI-assisted summary, checked against quoted sources · How we score