CVE-2026-102943 · AI agents & MCP
NO FIX YET · SEE WHAT TO DO
Dagu is a workflow engine with a web interface and an MCP server. An attacker holding a viewer-role API key can use the MCP dagu_read operation with the dag_spec target to read .yaml or .yml files outside the configured DAG directories.
first public Jul 26, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running Dagu before 2.11.0 that expose its MCP server or hand out viewer-role API keys. The bypass sits in the MCP dagu_read path, which skipped the HTTP middleware added for CVE-2026-33344, so the HTTP path is not the issue. Teams without the MCP operation in use or without third-party API key holders can treat this as low urgency.
Not affected if mcp-not-used, no-untrusted-api-keys, version-2.11.0-or-later
Who cares dagu, mcp, self-hosted, workflow-engine
dagu version2.11.0 or laterDagu is a workflow engine with a built-in Web user interface. Prior to version 2.11.0, its MCP dagu_read operation with target dag_spec invokes the DAG specification API directly, bypassing the HTTP middleware introduced for CVE-2026-33344. The underlying resolver does not restrict resolved paths to configured DAG directories. An authenticated attacker with a viewer-role API key can supply an absolute or traversing path to read .yaml or .yml files outside those directories that are accessible to the Dagu process. The affected operation does not provide write or execution capability. This issue is fixed in version 2.11.0.
This page as ·
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.