Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Low severity, with a CVSS score of 3.1, published 29 July 2026.
- Which products and versions are affected?
- @dynatrace-oss/dynatrace-mcp-server (npm) SEMVER:introduced=0,fixed=1.8.7.
- Is there a fix for This vulnerability?
- Yes. @dynatrace-oss/dynatrace-mcp-server (npm): upgrade to 1.8.7 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network.
- Am I affected?
- Check whether you run @dynatrace-oss/dynatrace-mcp-server (npm) 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
- @dynatrace-oss/dynatrace-mcp-server (npm): upgrade to 1.8.7 or later
npm install @dynatrace-oss/dynatrace-mcp-server@1.8.7
Technical details
The vulnerability is a missing authorization/approval check (CWE-862) in the create_dynatrace_notebook tool handler. The root cause is that while five other write tools (send_slack_message, send_email, send_event, create_workflow_for_notification, make_workflow_public) all call requestHumanApproval() at the start of execution to elicit operator consent via the MCP protocol, the create_dynatrace_notebook function was introduced in a separate release and left ungated. The attack requires network reachability to the HTTP-mode MCP server; when HTTP authentication is disabled, no credentials are required. An attacker can craft a JSON-RPC POST request to create a notebook with embedded DQL queries that execute under the identity of subsequent users who view the notebook, creating a stored cross-identity execution pattern. Patch: upgrade to version 1.8.7 or later.
Affected products
- Dynatrace MCP Server up to and including 1.8.6
Timeline
- 2026-07-29: disclosed: Advisory published on GitHub Security Advisory