# CVE-2026-123809: Dynatrace MCP Server: Workflow template injection via create_workflow_for_notification


- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-xrmj-5g4g-8987

## 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 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2026-123809?

1 open source package ship an affected version, including @dynatrace-oss/dynatrace-mcp-server.


| Package | Ecosystem | 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123809 and fix it if it is affected.

What it is: CVE-2026-123809 is a medium-severity vulnerability in dynatrace-oss dynatrace-mcp, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-123809 in the wild and no public exploit code.

Affected packages and fixed versions:
- @dynatrace-oss/dynatrace-mcp-server (npm): affected all versions; fixed in 2.0.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123809/ (Markdown: https://insights.sbomify.com/CVE-2026-123809/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123809
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123809
- OSV: https://osv.dev/vulnerability/CVE-2026-123809

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123809/
Summaries are generated and may contain mistakes; the official description above is the record.