# CVE-2026-123810: Dynatrace MCP Server: DQL injection via parameters not documented as DQL


- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-pqh8-p93p-2rx7

## What is CVE-2026-123810?

CVE-2026-123810 is a medium-severity vulnerability in dynatrace-oss dynatrace-mcp, published on 9 Nov 2026. 

### Official description

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.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-123810?

1 open source package ship an affected version, including @dynatrace-oss/dynatrace-mcp-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@dynatrace-oss/dynatrace-mcp-server` | npm | All versions | 2.1.1 |

## How do I fix CVE-2026-123810?

Upgrade @dynatrace-oss/dynatrace-mcp-server to 2.1.1 or later.

## Is CVE-2026-123810 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123810 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123810 and fix it if it is affected.

What it is: CVE-2026-123810 is a medium-severity vulnerability in dynatrace-oss dynatrace-mcp, published on 9 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123810 exists.

Affected packages and fixed versions:
- @dynatrace-oss/dynatrace-mcp-server (npm): affected all versions; fixed in 2.1.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123810/ (Markdown: https://insights.sbomify.com/CVE-2026-123810/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123810
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123810
- OSV: https://osv.dev/vulnerability/CVE-2026-123810

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123810/
Summaries are generated and may contain mistakes; the official description above is the record.