CVE-2026-33344
Directory Traversal in Dagu Workflow Engine API Endpoints
Publication date: 2026-03-24
Last updated on: 2026-03-26
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dagu | dagu | From 2.0.0 (inc) to 2.3.1 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-22 | The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in Dagu, a workflow engine with a built-in Web user interface, in versions from 2.0.0 to before 2.3.1. While the CREATE path was patched to validate DAG names and secure file path generation, other API endpoints such as GET, DELETE, RENAME, and EXECUTE still accept a {fileName} URL path parameter without proper validation. This allows attackers to use %2F-encoded forward slashes in the {fileName} parameter to traverse directories outside the intended DAGs directory, potentially accessing or manipulating unauthorized files.
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access or manipulation of files outside the designated DAGs directory. An attacker could exploit the directory traversal to read, delete, rename, or execute files that should be restricted, potentially compromising the integrity and confidentiality of the system. Given the CVSS score of 8.1 with high confidentiality and integrity impact, this could result in significant security breaches.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
The vulnerability has been patched in Dagu version 2.3.1. Immediate mitigation involves upgrading your Dagu installation to version 2.3.1 or later.
This patch ensures that all API endpoints properly validate the {fileName} parameter to prevent directory traversal attacks using %2F-encoded forward slashes.