# CVE-2026-123812: Dynatrace MCP Server: create_dynatrace_notebook missing the human-approval gate


- **Severity:** Low 3.7 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-pc2w-4mq8-32qw

## What is CVE-2026-123812?

CVE-2026-123812 is a low-severity vulnerability in dynatrace-oss dynatrace-mcp, published on 9 Nov 2026. 

### Official description

Dynatrace MCP Server is an MCP server for Dynatrace Observability. Prior to 1.8.7, the create_dynatrace_notebook registration in src/index.ts performs a persistent document-write action without calling requestHumanApproval, although the project's other write tools use that gate to obtain operator consent. A caller can create tenant-visible notebooks containing attacker-controlled Markdown or DQL content, and tenant users may later execute embedded DQL when opening the notebook. The tool also lacks a destructiveHint annotation that would signal its side effects to MCP clients. This issue is fixed in version 1.8.7.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-123812?

1 open source package ship an affected version, including @dynatrace-oss/dynatrace-mcp-server.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@dynatrace-oss/dynatrace-mcp-server` | npm | All versions | 1.8.7 |

## How do I fix CVE-2026-123812?

Upgrade @dynatrace-oss/dynatrace-mcp-server to 1.8.7 or later.

## Is CVE-2026-123812 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123812 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-123812 and fix it if it is affected.

What it is: CVE-2026-123812 is a low-severity vulnerability in dynatrace-oss dynatrace-mcp, published on 9 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-123812 exists.

Affected packages and fixed versions:
- @dynatrace-oss/dynatrace-mcp-server (npm): affected all versions; fixed in 1.8.7

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-123812/ (Markdown: https://insights.sbomify.com/CVE-2026-123812/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-123812
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-123812
- OSV: https://osv.dev/vulnerability/CVE-2026-123812

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-123812/
Summaries are generated and may contain mistakes; the official description above is the record.