CVE-2026-31886: critical vulnerability in dagu-org dagu
Dagu has a Path Traversal via `dagRunId` in Inline DAG Execution
Published
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.1epss 0.4%
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.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H
Affected products
dagu-org · daguRelated CVEs — dagu-org dagu
In the same product, most dangerous first.
CVE-2026-31882HIGHDagu SSE Authentication Bypass in Basic Auth ModeEPSS 0.8%CVE-2026-27598HIGHDagu: Path traversal in DAG creation allows arbitrary YAML file write outside DAGs directoryEPSS 0.6%CVE-2026-33344HIGHDagu has an incomplete fix for CVE-2026-27598: path traversal via %2F-encoded slashes in locateDAGEPSS 0.5%