Answer in brief
CVE-2026-123810 records a Medium severity (CVSS 4.3) vulnerability in Dynatrace MCP Server: DQL injection via parameters not documented as DQL. The current sources do not mark it as known exploited. The current feed maps dynatrace-oss/dynatrace-mcp (generic), @dynatrace-oss/dynatrace-mcp-server (npm), @dynatrace-oss/dynatrace-mcp-server (npm). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps dynatrace-oss/dynatrace-mcp (generic), @dynatrace-oss/dynatrace-mcp-server (npm), @dynatrace-oss/dynatrace-mcp-server (npm). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| dynatrace-oss/dynatrace-mcpgeneric | <2.1.1 | 2.1.1 |
| @dynatrace-oss/dynatrace-mcp-servernpm | <2.1.1 | 2.1.1 |
| @dynatrace-oss/dynatrace-mcp-servernpm | <2.1.1 | 2.1.1 |
Published upstream
Nov 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 9, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 2, 2026
Dynatrace MCP Server is an MCP server for Dynatrace Observability. Prior to 2.1.1, several read capabilities interpolate caller-controlled values into DQL without sufficient validation or escaping. The src/capabilities/find-monitored-entity-by-name.ts capability embeds entityNames in string searches, src/capabilities/list-problems.ts, src/capabilities/list-vulnerabilities.ts, and src/capabilities/list-exceptions.ts embed timeframe values, and src/capabilities/get-events-for-cluster.ts embeds timeframe, clusterId, and kubernetesEntityId. Crafted values can close string literals, append pipeline stages, or comment out the remaining intended query, allowing callers to bypass field selection, time-window, and result-display limits in tools marked readOnlyHint. The issue does not grant data access beyond the configured token's existing execute_dql capability, but it breaks the narrower auto-approved tool contract. This issue is fixed in version 2.1.1.
Quoted source text, attributed separately from HOL analysis.