CVE-2026-123810

Dynatrace read tools could exceed their intended query limits

Dynatrace · Dynatrace MCP Server

First documented disclosure · Review checkpoint

Summary

Inputs to monitoring tools could alter the query and return fields, time ranges or result sets outside the tool’s intended limits.

Severity and exploitation evidence

Medium · 4.3/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

Several MCP read tools inserted parameter values directly into Dynatrace Query Language expressions.

Conditions required

A caller has access to an affected MCP read tool connected to a Dynatrace tenant.

Potential impact

Queries could return additional data within the configured credential’s permissions. The project notes that the same token may already allow general queries.

Affected versions and configurations

The CNA lists versions before 2.1.1. The advisory table confirms affected versions through 1.8.5.

Fix and mitigation status

2.1.1.

Practical next steps

Upgrade to 2.1.1 or later and limit the underlying token to the dataset the tool should expose.

Operating lesson

Test input boundaries even when the exposed operation is read-only.

Evidence and limits

The public report does not establish access beyond the configured token’s tenant permissions.

Sources