LowGO-2026-4785CVE-2026-33344GHSA-ph8x-4jfv-v9v8
Dagu has an incomplete fix for CVE-2026-27598: path traversal via %2F-encoded slashes in locateDAG in github.com/dagu-org/dagu
Published 23 Mar 2026 · Updated 23 Mar 2026
Is your project on an affected github.com/dagu-org/dagu?
Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=1.30.4-0.20260221021317-e2ed589105d7 <1.30.4-0.20260319093346-7d07fda8f9de
- Fixed in
- 1.30.4-0.20260319093346-7d07fda8f9de
Update to the fixed version for your release line, for example:
go get github.com/dagu-org/dagu@v1.30.4-0.20260319093346-7d07fda8f9deDetails
Dagu has an incomplete fix for CVE-2026-27598: path traversal via %2F-encoded slashes in locateDAG in github.com/dagu-org/dagu
Is GO-2026-4785 in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected github.com/dagu-org/dagu, and gives you the command that fixes it.
More advisories for github.com/dagu-org/dagu
- LowCVE-2026-31886Dagu: Path Traversal via `dagRunId` in Inline DAG Execution in github.com/dagu-org/dagu · 13 Mar 2026
- CriticalCVE-2026-31886Dagu: Path Traversal via `dagRunId` in Inline DAG Execution · 13 Mar 2026
- LowCVE-2026-27598Dagu: Path traversal in DAG creation allows arbitrary YAML file write outside DAGs directory in github.com/dagu-org/dagu · 25 Feb 2026
- HighCVE-2026-27598Dagu: Path traversal in DAG creation allows arbitrary YAML file write outside DAGs directory · 24 Feb 2026
- LowCVE-2026-126752Dagu affected by unauthenticated RCE via inline DAG spec in default configuration in github.com/dagu-org/dagu · 23 Feb 2026
- CriticalCVE-2026-126752Dagu affected by unauthenticated RCE via inline DAG spec in default configuration · 19 Feb 2026
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.