Skip to content

AAK-MCP-DYNATRACE-CVE-2026-123811-001: Dynatrace MCP server 0.5.0 to 1.8.7: --http mode runs tool calls with no authentication

Severity
HIGH
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/mcp_cve_pins_2026_07.py
Auto-fixable
No.
SARIF name
DynatraceMcpHttpNoAuth

What it detects

The Dynatrace MCP server (npm @dynatrace-oss/dynatrace-mcp-server, dynatrace-oss/dynatrace-mcp) gives an MCP client the Dynatrace tenant it is configured for. Started with --http (or its alias --server), it handed every request to a stateless MCP transport with no token, session, Host or Origin check, so any caller that reached the port could run tools/call under the server's Dynatrace credentials: execute_dql reads logs, security events and user sessions, and from 1.2.0 create_dynatrace_notebook writes tenant-visible notebooks (CVE-2026-123811, CVSS 3.1 7.5, CWE-306, GHSA-p7w7-4929-vpj5). The listener bound 0.0.0.0 by default through 0.11.0 and 127.0.0.1 from 0.12.0. The default stdio transport is not affected. Checked in the published npm packages: the HTTP mode first ships in 0.5.0, 1.8.7 still checks nothing, and 2.0.0 adds a bearer check on MCP_BEARER_TOKEN and a Host allowlist, though it only warns when the variable is unset; 2.1.0 refuses to start without it. The repository is archived, 2.1.2 is the final release, and npm marks every version deprecated.

How to fix

Upgrade @dynatrace-oss/dynatrace-mcp-server to 2.0.0 or later and pin it, and set MCP_BEARER_TOKEN to a long random value before starting it with --http: 2.0.0 and 2.0.1 serve unauthenticated calls when it is unset, and 2.1.0 and later refuse to start without it. Better, run it over stdio or move to the Dynatrace Remote MCP Server the project points to: the package is archived and gets no further fixes.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-DYNATRACE-CVE-2026-123811-001

Limitations

Reports @dynatrace-oss/dynatrace-mcp-server from 0.5.0 below 2.0.0 where a package.json, lockfile or MCP config states the version, reporting a range that admits an affected version. It reads the version, not the transport: a server run over stdio, the default, is reported too, and no --http or --server argument is looked for, since the HTTP mode is normally started outside the client's config. 0.5.0-rc.1 to 0.5.0-rc.3, which have no HTTP mode, read as 0.5.0 and are reported. 2.0.0 and 2.0.1 still serve unauthenticated calls when MCP_BEARER_TOKEN is unset, which no version shows, and are not reported. latest was 2.1.2 on 2026-11-11 and states no version, so the README's @latest launch, an unversioned reference and a config that runs a global install by its executable name, mcp-server-dynatrace, are not reported. Releases from 0.5.0 below 2.0.0 also fire AAK-MCP-DYNATRACE-CVE-2026-123810-001. A file over 2 MB, or a lockfile over 32 MiB, is not read. A declaration nested more than 64 levels deep in package.json, a TOML manifest or an MCP config (an MCP server more than 62) is still judged, and reported without a line; a lockfile entry keeps its line at any depth.

References

  • CVE: CVE-2026-123811
  • OWASP MCP Top 10: MCP07:2025 (Insufficient Authentication & Authorization), MCP04:2025 (Software Supply Chain Attacks & Dependency Tampering)
  • OWASP Agentic Top 10: ASI03 (Identity and Privilege Abuse), ASI04 (Agentic Supply Chain Vulnerabilities)
  • Adversa AI MCP Top 25 (AAK-defined ids): ADV-AUTH-01 (Missing Authentication), ADV-SUPPLY-08 (MCP-Specific Vuln)
  • CSA AI Controls Matrix (AICM): IAM-01, STA-08

All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-DYNATRACE-CVE-2026-123811-001.md: the page then shows that text, with the registry reference appended under it.