{"items":[{"id":"NVI-00015102","kind":"vulnerability","title":"@dynatrace-oss/dynatrace-mcp-server has a workflow template injection via create_workflow_for_notification","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-xrmj-5g4g-8987"],"plain_summary":"GitHub lists this reviewed advisory for @dynatrace-oss/dynatrace-mcp-server. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-21fee643be8bdb6a6617a3125883a4e6"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-07-31T16:01:07.000Z","value":"4.2 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-21fee643be8bdb6a6617a3125883a4e6"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-21fee643be8bdb6a6617a3125883a4e6","url":"https://github.com/advisories/GHSA-xrmj-5g4g-8987","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-xrmj-5g4g-8987","publisher":"GitHub Advisory Database","observed_at":"2026-11-03T09:58:49.818Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-21fee643be8bdb6a6617a3125883a4e6"],"technology":"@dynatrace-oss/dynatrace-mcp-server","known_exclusions":[],"conditions_summary":"### Summary\nA template injection vulnerability in the `create_workflow_for_notification` tool lets a caller embed Jinja2 expressions that the Dynatrace workflow engine evaluates at runtime, exfiltrating event data to attacker-controlled destinations through a workflow that persists in the tenant after the MCP session ends.\n\n### Details\nThe `create_workflow_for_notification` tool interpolates three caller-supplied parameters (`teamName`, `problemType`, `channel`) directly into a Dynatrace Workflow definition. Dynatrace Workflows use Jinja2 templating: per the official documentation, `{{ ... }}` expressions in action inputs are evaluated at workflow runtime for every action except `Run Javascript` (which is carved out specifically to avoid code injection). A caller can therefore supply, for example, `teamName = \"{{ event() }}\"` and have the workflow engine evaluate that expression at runtime, serialising the full event object into the message body delivered to the Slack channel.\n\nThe vulnerable code is in `src/capabilities/create-workflow-for-problem-notification.ts`, lines 82-99:\n\n```typescript\nlet notif","public_affected_ranges":["< 2.0.0"]}],"null_published_at":"2026-11-03T10:03:26.548Z","source_updated_at":"2026-07-31T16:01:07.000Z","source_disclosed_at":"2026-07-31T16:01:07.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-03T09:58:49.818Z"}],"next_cursor":null,"snapshot_revision":"42594"}