https://db.gcve.eu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 11 Nov 2026 18:33:18 +0000 https://db.gcve.eu/vuln/fkie_cve-2026-123810 <p>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&#39;s existing execute_dql capability, but it breaks the narrower auto-approved tool contract. This issue is fixed in version 2.1.1.</p> <p>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&#39;s existing execute_dql capability, but it breaks the narrower auto-approved tool contract. This issue is fixed in version 2.1.1.</p> https://db.gcve.eu/vuln/fkie_cve-2026-123810 https://db.gcve.eu/vuln/ghsa-pqh8-p93p-2rx7 <p><strong>Affected:</strong> npm: @dynatrace-oss/dynatrace-mcp-server</p> <p>### Summary A DQL injection vulnerability in several read tools lets a caller bypass the tools&#39; documented field-scope, time-window, and display caps by injecting DQL pipeline stages through parameters typed as identifiers.</p> <p>### Details Several tools interpolate caller-supplied parameters directly into DQL query strings without quoting or escaping. The affected parameters are documented in their Zod schemas as identifiers or constrained shorthand (such as `&#34;24h&#34;` timeframe values or Kubernetes UIDs) - not as DQL expressions. The interpolation lets a caller break out of string literals, append arbitrary DQL pipeline stages, and use `//` line comments (documented in the [Dynatrace DQL language reference](https://docs.dynatrace.com/docs/discover-dynatrace/platform/grail/dynatrace-query-language/dql-reference)) to discard the rest of the intended query.</p> <p>The marginal-privilege ceiling is low because the operator&#39;s token also exposes `execute_dql` with full DQL access. What the injection grants is the ability to bypass the affected tools&#39; contract: the `readOnlyHint: true` annotation that MCP clients may treat as a signal to auto-approve, the per-tool field selection (e.g., `| fields id, name, type`), the display caps (`maxProblemsToDisplay`, `maxVulnerabilitiesToDisplay`, `maxEntitiesToDisplay`), and the time-window bounds.</p> <p>The vulnerable interpolations are:</p> <p>| File | Line | Parameter | Interpolation | |------|------|-----------|---------------| | `src/capabilities/find-monitor…</p> <p><strong>Affected:</strong> npm: @dynatrace-oss/dynatrace-mcp-server</p> <p>### Summary A DQL injection vulnerability in several read tools lets a caller bypass the tools&#39; documented field-scope, time-window, and display caps by injecting DQL pipeline stages through parameters typed as identifiers.</p> <p>### Details Several tools interpolate caller-supplied parameters directly into DQL query strings without quoting or escaping. The affected parameters are documented in their Zod schemas as identifiers or constrained shorthand (such as `&#34;24h&#34;` timeframe values or Kubernetes UIDs) - not as DQL expressions. The interpolation lets a caller break out of string literals, append arbitrary DQL pipeline stages, and use `//` line comments (documented in the [Dynatrace DQL language reference](https://docs.dynatrace.com/docs/discover-dynatrace/platform/grail/dynatrace-query-language/dql-reference)) to discard the rest of the intended query.</p> <p>The marginal-privilege ceiling is low because the operator&#39;s token also exposes `execute_dql` with full DQL access. What the injection grants is the ability to bypass the affected tools&#39; contract: the `readOnlyHint: true` annotation that MCP clients may treat as a signal to auto-approve, the per-tool field selection (e.g., `| fields id, name, type`), the display caps (`maxProblemsToDisplay`, `maxVulnerabilitiesToDisplay`, `maxEntitiesToDisplay`), and the time-window bounds.</p> <p>The vulnerable interpolations are:</p> <p>| File | Line | Parameter | Interpolation | |------|------|-----------|---------------| | `src/capabilities/find-monitor…</p> https://db.gcve.eu/vuln/ghsa-pqh8-p93p-2rx7