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 31 July 2026.

Which products and versions are affected?

@dynatrace-oss/dynatrace-mcp-server (npm) SEMVER:introduced=0,fixed=2.0.0.

Is there a fix for This vulnerability?

Yes. @dynatrace-oss/dynatrace-mcp-server (npm): upgrade to 2.0.0 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, in a software library.

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.

Dynatrace MCP Server HTTP authentication bypass

Severity: low · CVSS 3.1 · Published 2026-07-31

The Dynatrace MCP Server, a tool that integrates Dynatrace monitoring and data analysis capabilities, can be run in HTTP mode without any authentication checks. An attacker with network access can invoke sensitive operations under the server's own Dynatrace credentials, such as reading logs and security events or creating notebooks in the tenant, without providing any credentials.

Technologies: @dynatrace-oss/dynatrace-mcp-server (npm). Vendors: npm.

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 31 July 2026.
Which products and versions are affected?: @dynatrace-oss/dynatrace-mcp-server (npm) SEMVER:introduced=0,fixed=2.0.0.
Is there a fix for This vulnerability?: Yes. @dynatrace-oss/dynatrace-mcp-server (npm): upgrade to 2.0.0 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, in a software library.
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 2.0.0 or later
```
npm install @dynatrace-oss/dynatrace-mcp-server@2.0.0
```

Technical details

The vulnerability is an authentication bypass in the HTTP transport mode (--http flag) of @dynatrace-oss/dynatrace-mcp-server. When HTTP mode is enabled, the server creates a StreamableHTTPServerTransport that does not validate bearer tokens, session IDs, host, or origin before dispatching JSON-RPC tool calls. An unauthenticated network attacker can send a raw JSON-RPC request (e.g., tools/call) without an Authorization header and have it executed under the server's stored Dynatrace credentials. Two high-impact tools are confirmed reachable: execute_dql (allows arbitrary DQL queries reading logs, security events, and user sessions) and create_dynatrace_notebook (allows writing notebooks to the tenant). The flaw affects versions ≤1.8.7; version 2.0.0 and later include a patch that requires an HTTP auth token.

Affected products

Dynatrace OSS dynatrace-mcp-server <= 1.8.7

Timeline

2026-07-31: disclosed
2026-06-09: patched: Patch released in version 2.0.0

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.