Dynatrace MCP Server: Unauthenticated HTTP MCP Tool Invocation in `@dynatrace-oss/dynatrace-mcp-server`
Only affects @dynatrace-oss/dynatrace-mcp-server when started with the --http option, which has no authentication. Fixed in 2.0.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 2.0.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Server started with the --http option (HTTP transport mode). Attacker must be able to reach the server port over the network (deployments using --host 0.0.0.0 are most exposed).
- Published
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 20/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The Dynatrace MCP Server package (`@dynatrace-oss/dynatrace-mcp-server`), when started with its `--http` option, can be reached remotely without logging in and lets an attacker run its tools under the server's configured Dynatrace credentials. This allows reading Grail data such as logs, security events, and user sessions through `execute_dql`, or creating tenant-visible notebooks.
Read the original description
Dynatrace MCP Server is an MCP server for Dynatrace Observability. Prior to 2.0.0, a server started with the --http option accepts JSON-RPC tools/call requests without authentication, session validation, or Host and Origin protections before dispatching them under the server's configured Dynatrace credentials. A network-reachable caller can invoke execute_dql to read logs, security events, user sessions, and other Grail data, or invoke create_dynatrace_notebook to create tenant-visible notebooks. The send_event path is not affected because its requestHumanApproval gate blocks this attack path, and reset_grail_budget only demonstrates dispatch without accessing Dynatrace data. This issue is fixed in version 2.0.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure12/25Specific setups only, reachable over the network without a login
- Reach?/20Unknown. No tracked technology or package matched
- Severity7.5/10CVSS 7.5
- No patch0/5No signal
What would change the score
- Would score about 70 if added to CISA KEV
- Would score about 65 if CISA's SSVC rates exploitation active
What to do
Check whether your setup matches what the bug needs.
Server started with the --http option (HTTP transport mode). Attacker must be able to reach the server port over the network (deployments using --host 0.0.0.0 are most exposed).Upgrade to a fixed version: 2.0.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- dynatrace-oss dynatrace-mcp
fixed in 2.0.0
Evidence 5
- Advisory
- Repository
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123811
Is CVE-2026-123811 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The HTTP transport mode (--http flag) accepts tool calls without authentication. Anyone who can reach the server port can invoke tools under the server's Dynatrace credentials, such as reading logs and security events through execute_dql or creating notebooks with create_dynatrace_notebook.Source: github.com
Which versions are affected by CVE-2026-123811?
dynatrace-mcp: before 2.0.0.Source: cve.now feed data
Am I affected, and how do I check?
The affected product is the dynatrace-oss dynatrace-mcp package before version 2.0.0, and the exposure depends on the HTTP transport mode being started. Check the startup command or configuration for the --http option, and check the --host setting, since deployments bound to 0.0.0.0 are most exposed.Source: github.com
How do I fix CVE-2026-123811?
Upgrade dynatrace-mcp to version 2.0.0 or later.Source: github.com