Dagu MCP DAG specification read bypasses path containment and workspace isolation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| dagucloud | dagu | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Dagucloud | Dagu |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-5m6c-38r8-5w76 | Dagu MCP DAG specification read bypasses path containment and workspace isolation |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.413% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Dagucloud
Dagucloud dagu |
|
| Vendors & Products |
Dagucloud
Dagucloud dagu |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | Dagu 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. | |
| Title | Dagu MCP DAG specification read bypasses path containment and workspace isolation | |
| Weaknesses | CWE-22 CWE-863 |
|
| References |
| |
| Metrics |
cvssV3_1
|