Quick answers
- Is CVE-2026-123809 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123809 being exploited in the wild.
- How severe is CVE-2026-123809?
- Medium severity, with a CVSS score of 4.2, published 9 November 2026.
- Which products and versions are affected?
- Dynatrace-Mcp-Server prior to 2.0.0.
- Is there a fix for CVE-2026-123809?
- Yes: fixed in 2.0.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123809 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-123809?
- Check whether you run Dynatrace-Mcp-Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.0.0
Technical details
The create_workflow_for_notification tool fails to sanitize caller-controlled inputs (teamName, problemType, channel) before inserting them into Dynatrace workflows, allowing Jinja2 template injection. When the workflow executes with a valid Slack connector, attackers can use expressions like event() to access and exfiltrate event and tenant metadata. The created workflow persists in the tenant even after the MCP session ends and defaults to tenant-visible unless explicitly marked private.
Affected products
- Dynatrace MCP Server prior to 2.0.0
Timeline
- 2026-11-09: disclosed: CVE-2026-123809 published
- 2026-06-16: patched: v2.0.0 released with create_workflow_for_notification tool removed