CVE-2026-123809

Workflow inputs could become executable templates in Dynatrace

Dynatrace · Dynatrace MCP Server

First documented disclosure · Review checkpoint

Summary

Text supplied to the notification workflow tool could be interpreted later as a template in a saved workflow.

Severity and exploitation evidence

Medium · 4.2/10 · CVSS 3.1. Severity source.

Exploitation not established: The reviewed sources describe the vulnerability and its conditions. They do not identify malicious exploitation.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

User-provided workflow fields were embedded in a template without treating them as literal data.

Conditions required

A caller can create the workflow and its creation is approved. Delivery of data to a messaging channel also requires a configured connector.

Potential impact

A later workflow execution could disclose event or tenant data through the configured destination. The placeholder connector used in testing did not deliver a message.

Affected versions and configurations

The CNA lists versions before 2.0.0. The upstream table confirms affected versions through 1.8.5.

Fix and mitigation status

2.0.0.

Practical next steps

Upgrade to 2.0.0 or later and review previously created notification workflows and their destinations.

Operating lesson

Validate the completed workflow before an approval authorizes persistent automation.

Evidence and limits

The project demonstrated template evaluation. Delivery and data exposure depend on a working connector.

Sources