CVSS 3.1
4.2 mediumCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:NCVE-2026-123809
Medium (4.2) in dynatrace-oss dynatrace-mcp. EPSS 0.2% estimated probability of exploitation activity in the next 30 days. Fixed in @dynatrace-oss/dynatrace-mcp-server 2.0.0.
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.
Severity
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 7th percentile. Scored 2026-11-10. A forecast for this CVE across the internet, not for your own systems.
- CWE
- CWE-1336 Improper Neutralization of Special Elements Used in a Template Engine
- Published
- Assigned by
- GitHub_M (CNA)
- NVD analysis
- Not in the NVD yet
- Record from
- the CVE List, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-123809 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-123809?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-123809?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-123809 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| dynatrace-oss dynatrace-mcp | < 2.0.0 |
Packages (OSV)
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-xrmj-5g4g-8987 | npm | @dynatrace-oss/dynatrace-mcp-server | <2.0.0 | 2.0.0 |