CVE-2026-33344
Received Received - Intake
Directory Traversal in Dagu Workflow Engine API Endpoints

Publication date: 2026-03-24

Last updated on: 2026-03-26

Assigner: GitHub, Inc.

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-24
Last Modified
2026-03-26
Generated
2026-06-16
AI Q&A
2026-03-24
EPSS Evaluated
2026-06-15
NVD
CVE-2026-33344
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
dagu dagu From 2.0.0 (inc) to 2.3.1 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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 Quick Actions
Instant insights powered by AI
Executive Summary

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.

Impact Analysis

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.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

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.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-33344. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart