Quick answers
- Is CVE-2026-123810 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-123810 being exploited in the wild.
- How severe is CVE-2026-123810?
- Medium severity, with a CVSS score of 4.3, published 9 November 2026.
- Which products and versions are affected?
- Dynatrace-Mcp-Server before 2.1.1.
- Is there a fix for CVE-2026-123810?
- Yes: fixed in 2.1.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-123810 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-123810?
- Check whether you run Dynatrace-Mcp-Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 2.1.1
Technical details
The vulnerability is a DQL injection flaw in multiple read capabilities that interpolate unsanitized caller-controlled values directly into query strings. Affected components include find-monitored-entity-by-name.ts (entity names), list-problems.ts, list-vulnerabilities.ts, list-exceptions.ts (timeframe values), and get-events-for-cluster.ts (timeframe, clusterId, kubernetesEntityId). An authenticated attacker with access to these tools can craft input values to close string literals, append pipeline stages, or comment out query portions, effectively bypassing intended query restrictions marked as readOnlyHint.
Affected products
- Dynatrace MCP Server before 2.1.1
Timeline
- 2026-11-09: disclosed
- 2026-07-14: patched