Threat Intelligence Database

CVE-2026-33344 is a high-severity path traversal vulnerability in the dagu workflow engine versions 2.0.0 up to but not including 2.3.1. The flaw arises because several API endpoints (GET, DELETE, RENAME, EXECUTE) fail to properly validate the {fileName} URL parameter, allowing attackers to use encoded forward slashes (%2F) to traverse directories outside the intended DAGs directory. This can lead to unauthorized access and modification of files, impacting confidentiality and integrity. The vulnerability requires network access and low privileges but no user interaction. It was patched in version 2.3.

HighVulnerabilityUnited StatesGermanyUnited Kingdom+7#cve#cve-2026-33344#cwe-22

Dagu is a workflow engine with a built-in Web user interface. Prior to 2.2.4, the 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. This vulnerability is fixed in 2.2.4.

CriticalVulnerabilityUnited StatesGermanyUnited Kingdom+7#cve#cve-2026-31886#cwe-22

Dagu is a workflow engine with a built-in Web user interface. In versions up to and including 1.16.7, the `CreateNewDAG` API endpoint (`POST /api/v1/dags`) does not validate the DAG name before passing it to the file store. An authenticated user with DAG write permissions can write arbitrary YAML files anywhere on the filesystem (limited by the process permissions). Since dagu executes DAG files as shell commands, writing a malicious DAG to the DAGs directory of another instance or overwriting config files can lead to remote code execution. Commit e2ed589105d79273e4e6ac8eb31525f765bb3ce4 fixes the issue.

HighVulnerabilityUnited StatesGermanyUnited Kingdom+7#cve#cve-2026-27598#cwe-22