Public vulnerability disclosure

CVE-2026-123809

Dynatrace MCP Server: Workflow template injection via create_workflow_for_notification

publishedCWE-1336

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.

Technical severity4.2 mediumCVSS 3.1 · CNA: GitHub_M
Published2026-11-09Source updated 2026-11-09
Collected2026-11-092 attributed sources

Fixes and workarounds

Fix

@dynatrace-oss/dynatrace-mcp-server (npm): OSV reports a fixed version 2.0.0. Check the advisory for supported release branches.

Source: OSV GHSA-xrmj-5g4g-8987

Affected products and versions

Affected products, source version ranges and reporting authorities
ProductVersionsAuthority
dynatrace-mcp
dynatrace-oss
< 2.0.0 (affected) CNA: GitHub_M
@dynatrace-oss/dynatrace-mcp-server

@dynatrace-oss/dynatrace-mcp-server
npm
≥ 0; < 2.0.0 (affected, semver); OSV events: introduced 0; fixed 2.0.0
Source events (semver)
[
  {
    "introduced": "0"
  },
  {
    "fixed": "2.0.0"
  }
]

Other versions: unaffected
OSV GHSA-xrmj-5g4g-8987

Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.

CVSS assessments

CVSS scores, vectors and reporting authorities
Version / scoreVectorAuthority
3.1 / 4.2
medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:L/A:NCNA: GitHub_M

Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

References

For agents and automation

Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.

Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.

Endpoints and access details

https://api.y2.dev/api/v2/cyber/cves
https://api.y2.dev/api/v2/cyber/cves/{cveId}

A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.

For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.

Agent access JSON · OpenAPI · CVE API guide