<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Wed, 11 Nov 2026 18:05:25 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-123812</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-123812</link>
      <description>&lt;p&gt;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&amp;#39;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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&amp;#39;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-123812</guid>
    </item>
    <item>
      <title>GHSA-pc2w-4mq8-32qw — @dynatrace-oss/dynatrace-mcp-server's create_dynatrace_notebook missing the human-approval gate</title>
      <link>https://db.gcve.eu/vuln/ghsa-pc2w-4mq8-32qw</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @dynatrace-oss/dynatrace-mcp-server&lt;/p&gt;
&lt;p&gt;### Summary
A missing human-approval gate on the `create_dynatrace_notebook` tool allows a caller to create persistent tenant-visible documents containing arbitrary content (including embedded DQL that other users execute when opening the notebook) without operator consent.&lt;/p&gt;
&lt;p&gt;### Details
`dynatrace-mcp-server` registers six write tools: `send_slack_message`, `send_email`, `send_event`, `create_workflow_for_notification`, `make_workflow_public`, and `create_dynatrace_notebook`. Five of these call `requestHumanApproval()` before executing the side-effect, which elicits the operator&amp;#39;s explicit consent through the MCP elicitation protocol. The CHANGELOG explicitly states these approval gates were added &amp;#34;to ensure user consent and prevent unintended actions.&amp;#34;&lt;/p&gt;
&lt;p&gt;`create_dynatrace_notebook` does not call `requestHumanApproval()`. The tool was introduced in a separate release from the approval-gate retrofit and was left ungated. As a result, a caller can create persistent, tenant-visible Dynatrace notebooks containing arbitrary content with no operator confirmation. Notebooks can include embedded DQL queries that later execute under the permissions of any tenant user who opens them.&lt;/p&gt;
&lt;p&gt;The vulnerable code is in `src/index.ts`, lines 1563-1601:&lt;/p&gt;
&lt;p&gt;```typescript
tool(
  &amp;#39;create_dynatrace_notebook&amp;#39;,
  &amp;#39;Create Dynatrace Notebook&amp;#39;,
  &amp;#39;Create a new notebook in the Dynatrace platform ...&amp;#39;,
  {
    name: z.string().describe(/* ... */),
    description: z.string().optional().describe(/* ... */),…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: @dynatrace-oss/dynatrace-mcp-server&lt;/p&gt;
&lt;p&gt;### Summary
A missing human-approval gate on the `create_dynatrace_notebook` tool allows a caller to create persistent tenant-visible documents containing arbitrary content (including embedded DQL that other users execute when opening the notebook) without operator consent.&lt;/p&gt;
&lt;p&gt;### Details
`dynatrace-mcp-server` registers six write tools: `send_slack_message`, `send_email`, `send_event`, `create_workflow_for_notification`, `make_workflow_public`, and `create_dynatrace_notebook`. Five of these call `requestHumanApproval()` before executing the side-effect, which elicits the operator&amp;#39;s explicit consent through the MCP elicitation protocol. The CHANGELOG explicitly states these approval gates were added &amp;#34;to ensure user consent and prevent unintended actions.&amp;#34;&lt;/p&gt;
&lt;p&gt;`create_dynatrace_notebook` does not call `requestHumanApproval()`. The tool was introduced in a separate release from the approval-gate retrofit and was left ungated. As a result, a caller can create persistent, tenant-visible Dynatrace notebooks containing arbitrary content with no operator confirmation. Notebooks can include embedded DQL queries that later execute under the permissions of any tenant user who opens them.&lt;/p&gt;
&lt;p&gt;The vulnerable code is in `src/index.ts`, lines 1563-1601:&lt;/p&gt;
&lt;p&gt;```typescript
tool(
  &amp;#39;create_dynatrace_notebook&amp;#39;,
  &amp;#39;Create Dynatrace Notebook&amp;#39;,
  &amp;#39;Create a new notebook in the Dynatrace platform ...&amp;#39;,
  {
    name: z.string().describe(/* ... */),
    description: z.string().optional().describe(/* ... */),…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-pc2w-4mq8-32qw</guid>
    </item>
  </channel>
</rss>
