CVE-2026-123809: dynatrace-mcp · Template Injection
Affects dynatrace-mcpSource CVE Database V5
Not known to be exploited · CVSS 4.2 Medium : upgrade to 2.0.0 when convenient.
Data as of 9 Nov 2026, 21:06 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 4.2 |
|---|
- Patch
- Available – fixed in 2.0.0
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 9 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 9 Nov 2026.
What to do
Upgrade dynatrace-mcp to 2.0.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| dynatrace-ossdynatrace-mcp | Affected
| Fixed in
|
AI-suggested
Upgrade Dynatrace MCP Server to version 2.0.0 or later, where this vulnerability is fixed. No additional mitigation is required if the upgrade is applied. Until then, avoid using untrusted input in workflow parameters and restrict operator approval of prompts that display template fragments.
Description
A vulnerability in Dynatrace MCP Server versions prior to 2.0.0 allows improper neutralization of Jinja2 template expressions in certain workflow parameters. This can lead to unintended evaluation of attacker-controlled template code within persistent workflows, potentially disclosing event or tenant metadata via Slack actions if a valid Slack connector is configured. The issue is fixed in version 2.0.0.