YAML file read and deletion via encoded traversal
Published Mar 24, 2026 · Updated Mar 24, 2026
Path traversal in Dagu 2.0.0 through 2.3.0 allows remote attackers to read or delete server-side YAML files through API requests. GET, DELETE, RENAME, and EXECUTE handlers decode %2F in the fileName path parameter and pass the result to locateDAG, whose findDAGFile path resolution checks only file existence and a YAML extension rather than containment within the DAGs directory. Any authenticated user can reach the read and delete paths regardless of role; deployments with auth.mode=none expose them without credentials, and access is limited to readable or removable .yaml and .yml files.
Summary
What happened
Path traversal in Dagu 2.0.0 through 2.3.0 allows remote attackers to read or delete server-side YAML files through API requests. GET, DELETE, RENAME, and EXECUTE handlers decode %2F in the fileName path parameter and pass the result to locateDAG, whose findDAGFile path resolution checks only file existence and a YAML extension rather than containment within the DAGs directory. Any authenticated user can reach the read and delete paths regardless of role; deployments with auth.mode=none expose them without credentials, and access is limited to readable or removable .yaml and .yml files.
The record
- CVE
- CVE-2026-33344
- Published
- Mar 24, 2026
- Updated
- Mar 24, 2026
- Vendor
- Dagu
- Product
- Dagu
- Classifications
- CWE-22, T1070.004, T1005
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 24, 2026CVE publishedPublication date reported by the CVE source.
- Mar 24, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 2.0.0, < 2.3.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Store-level and HTTP-level encoded-slash traversal proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo