Dagu
Dagu has an incomplete fix for CVE-2026-27598: path traversal via %2F-encoded slashes in locateDAG
Dagu is a workflow engine with a built-in Web user interface. From version 2.0.0 to before version 2.3.1, the fix for CVE-2026-27598 added ValidateDAGName to CreateNewDAG and rewrote generateFilePath to use filepath.Base. This patched the CREATE path. The remaining API endpoints - GET, DELETE, RENAME, EXECUTE - all pass the {fileName} URL path parameter to locateDAG without calling ValidateDAGName. %2F-encoded forward slashes in the {fileName} segment traverse outside the DAGs directory. This issue has been patched in version 2.3.1.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2.0.0, < 2.3.1
Fixed in 2.3.1
Mitigation
Upgrade dagu to 2.3.1 or later.
References
Timeline
Days relative to CVE publicationFirst public PoC 226 days after publication; not in CISA KEV. First PoC: nuclei template: dagu <= 2.3.0 - Path Traversal via Encoded Slashes in DAG Name (nuclei template, 6 Nov 2026).
PoC repositories
Found on GitHub.No PoC repositories found yet.
Other public exploits
Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.| Source | Title | Published | Found by us |
|---|---|---|---|
| nuclei template | nuclei template: dagu <= 2.3.0 - Path Traversal via Encoded Slashes in DAG Name | 6 Nov 2026 | 14 Nov 2026 |