GHSA-m4q3-457p-hh2x: Dagu: Path Traversal via `dagRunId` in Inline DAG Execution
1. Vulnerability SummaryThe `dagRunId` request field accepted by the inline DAG execution endpoints is passed directly into `filepath.Join` to construct a temporary directory path without any format validation. Go's `filepath.Join` resolves `..` segments lexically, so a caller can supply a value such as `".."` to redirect the computed directory outside the intended `/tmp/<name>/<id>` path. A deferred cleanup function that calls `os.RemoveAll` on that directory then runs unconditionally when the HTTP handler returns, deleting whatever directory the traversal resolved to.With `dagRunId` set to `".."`, the resolved directory is the system temporary directory (`/tmp` on Linux). On non-root deployments, `os.RemoveAll("/tmp")` removes all files in `/tmp` owned by the dagu process user, disrupting every concurrent dagu run that has live temp files. On root or Docker deployments, the call removes the entire contents of `/tmp`, causing a system-wide denial of service.2. This Is Not a Duplicate of Existing AdvisoriesTwo security advisories are already published for dagu. This vulnerability is distinct from both.**GHSA-6qr9-g2xw-cw92** fixed the fact that the default authentication mode was `none`, allowing unauthenticated access to the inline execution endpoint. That advisory covers authentication bypass. The `dagRunId` path traversal described here is a separate input-validation flaw in `loadInlineDAG()` that exists regardless of whether authentication is required and was not addressed by that fix.**CVE-2026-27598** fixed a path traversal in the DAG creation endpoint (`POST /api/v1/dags`) via the `name` field. The fix added `filepath.Base()` and a base-directory prefix check inside `generateFilePath()`. That fix applies only to `generateFilePath()` in `dags.go`. The function `loadInlineDAG()` in `dagruns.go` has no equivalent guard on its `dagRunID` argument and was not part of that patch.3. Vulnerable Code**File**: `internal/service/frontend/api/v1/dagruns.go`The `loadInlineDAG` function (lines 202-267) constructs the temp directory at line 234:`dagRunID` is user-supplied. No validation of the value occurs before this line. The cleanup closure is then registered:In `ExecuteDAGRunFromSpec` (lines 52-119), the cleanup is deferred unconditionally:The same pattern appears in `EnqueueDAGRunFromSpec` (lines 122-200), line 160:**Why the OpenAPI schema pattern does not prevent this:**The `DAGRunId` schema in `api/v1/api.yaml` (line 5738) declares:This pattern excludes `.` and `/`, which would block path traversal values. However, enforcement of that pattern depends on the OpenAPI validator middleware, which is only activated when `StrictValidation` is `true`. That setting is defined in `internal/cmn/config/config.go`:It is not present in the `Definition` struct (`definition.go`) and carries no `mapstructure` tag, which means viper/mapstructure can never populate it from a YAML configuration file; it therefore cannot be set in the config loader (`loader.go`) and its value is always the Go zero value for `bool`, which is `false`. The loader test at line 165 of `loader_test.go` confirms that `StrictValidation` is `false` even after loading a comprehensive configuration file that exercises every configurable option — because there is no mechanism by which it could ever be `true`. The validator middleware is never registered for any standard dagu deployment.The file `dagruns.go` defines a `sanitizeFilename` helper at line 36 that replaces characters outside `[a-zA-Z0-9._-]` with underscores. This function is called when constructing log filenames (lines 422, 566, 1127, and 1211) and is never applied to `dagRunID` before the `filepath.Join` call. No validation or sanitization of `dagRunID` for path separator characters exists anywhere in the request-to-`filepath.Join` pipeline.4. Attack ConditionsThe attacker must be authenticated with a role of `operator`, `developer`, `manager`, or `admin` (any role for which `CanExecute()` returns true).The server permission `PermissionRunDAGs` must be enabled. This is the default (`true` as set in `loader.go` lines 353-356).On dagu versions 1.30.3 and earlier, where the default authentication mode was `none`, no authentication is required at all.5. Attack ScenarioStep 1: AuthenticateFor versions with `auth.mode: none`, authentication is not required and the `Authorization` header can be omitted.Step 2: Send the malicious requestStep 3: What happens inside the server`request.Body.DagRunId` is `".."`. This value is copied to `dagRunId` at line 72 without modification.`loadInlineDAG` is called with `dagRunID = ".."` and no `name` parameter, so `nameHint = "inline"`. Because `name` is nil, the `else` branch at lines 214-231 runs first: `spec.LoadYAML` parses the spec content and `dag.Validate()` checks its structure. This pre-validation operates entirely on the YAML content; it has no knowledge of `dagRunID`. The exploit spec (`steps:\n  - name: s\n    command: id\n`) passes this check. The `nameHint` variable is not updated by this parse — it stays `"inline"` regardless of any `name` field inside the spec YAML. Control reaches line 234 only after the spec is accepted.Line 234 executes:(`filepath.Join` calls `filepath.Clean` on the joined result, resolving `..` lexically.)`os.MkdirAll("/tmp", 0o750)` succeeds because `/tmp` already exists.The cleanup closure captures `tmpDir = "/tmp"`:The spec is written to `filepath.Join("/tmp", "inline.yaml")` = `/tmp/inline.yaml` and loaded via `spec.Load` (line 256). The load succeeds.`loadInlineDAG` returns `dag, cleanup, nil`.`defer cleanup()` is registered in `ExecuteDAGRunFromSpec`.The handler builds the 200 response object. In Go, deferred functions execute during the function's return sequence — before control returns to chi's server wrapper. The deferred cleanup therefore fires first: `os.RemoveAll("/tmp")` runs and removes the target directory.The handler returns the response object to chi. Chi serializes it and sends the HTTP 200 to the client. The 200 is delivered successfully because the response content was already constructed before the defer ran; the directory deletion does not affect the HTTP response.Step 4: ResultOn non-root deployments: all files in `/tmp` owned by the dagu process user are removed (Linux sticky bit prevents deletion of files owned by other users). Any concurrent dagu runs that have live temp files in `/tmp` lose those files and fail.On root or Docker deployments (where dagu runs as root inside a container, which is a common production pattern): all contents of `/tmp` are removed, affecting every process on the system that uses `/tmp` for temporary storage.The attack can be sent repeatedly without any cooldown, maintaining the denial-of-service condition.6. Proof of ConceptOne-liner (against auth-mode-none instance)Automated PoC scriptSave as `poc.py` and run with `python3 poc.py`:Local test setup (no existing dagu installation needed)Variant: target the enqueue endpointBoth endpoints are affected via the same `loadInlineDAG` call:Variant: file write outside /tmpWith a `dagRunId` value that traverses to a known writable directory, the spec content is written there as `<nameHint>.yaml` before the cleanup removes that directory:This writes `/home/dagu/dags/payload.yaml`, executes it, then calls `os.RemoveAll("/home/dagu/dags")`, deleting the entire DAGs directory. The exact path depends on the deployment but can be inferred from error messages or default paths.7. Impact**Denial of Service (primary)**On every deployment, an authenticated operator can send one request to trigger `os.RemoveAll` on a directory outside the intended temp subdirectory. With `dagRunId=".."`, the target is `/tmp`. On a non-root deployment with Linux sticky bit semantics, all temp files in `/tmp` created by the dagu user are deleted. Any running dagu workflow that depends on temp files in progress is interrupted. The attack can be repeated continuously with no rate limiting, preventing recovery.On Docker-based deployments where dagu runs as root inside a container (a common pattern for dagu installations), `os.RemoveAll("/tmp")` removes all contents of `/tmp` inside the container. This affects every process in the container that uses `/tmp`, including shared libraries unpacked at runtime, unix sockets, and lock files.**Arbitrary file write (secondary)**The spec YAML content provided by the attacker is written to `filepath.Join(tmpDir, nameHint+".yaml")` where both `tmpDir` and `nameHint` can be influenced. If the attacker knows or can guess the path of a directory writable by the dagu process (for example, the DAGs directory), they can write arbitrary YAML content there. Because `spec.Load` reads from that path and executes the spec, this also provides a mechanism for persisting a workflow definition containing attacker-controlled commands in the DAGs directory before the cleanup removes it.**Deletion of the DAGs directory (combined)**The combination of the file write and the cleanup allows an authenticated operator to permanently delete the entire DAGs directory in a single request by pointing `dagRunId` at that path. This destroys all workflow definitions for all users of the dagu instance.8. Affected VersionsThe `loadInlineDAG` function and both calling handlers (`ExecuteDAGRunFromSpec` and `EnqueueDAGRunFromSpec`) are present in the current `main` branch. The vulnerability has existed since these endpoints were introduced. No fix is present as of the review date of 2026-02-24.Authentication requirements differ by version:Versions 1.30.3 and earlier: default `auth.mode` was `none`, so this is exploitable without credentialsVersions after 1.30.3: default `auth.mode` is `builtin`, so operator-level credentials are required9. Recommended FixValidate `dagRunID` before use in `loadInlineDAG`. The OpenAPI schema already defines the correct pattern. Enforce it at the application layer:As a defense-in-depth measure, verify that the resolved `tmpDir` is actually inside the expected base after joining:The same fix must be applied to both `ExecuteDAGRunFromSpec` and `EnqueueDAGRunFromSpec`. Additionally, enabling `StrictValidation: true` as the default configuration would provide an extra layer of enforcement at the API boundary.
CVSS v3.1: 9.1