VulnerabilityPublished 24 Mar 2026

CVE-2026-33344: dagu · Path Traversal

Affects daguSource CVE Database V5

Compare

Mentioned vulnerabilities

CVE-2026-27598

Not known to be exploited · CVSS 8.1 High : upgrade to 2.3.1 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score

8.1High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 2.3.1

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 24 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade dagu and dagu-org/dagu to 2.3.1.

Affected software

Product	Affected	Fixed in
dagu-orgdagu	Affected >=2.0.0 <2.3.1	Fixed in 2.3.1
GitHubdagu-org/dagu`pkg:github/dagu-org/dagu`Other threats	Affected >=2.0.0 <2.3.1	Fixed in 2.3.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade dagu to version 2.3.1 or later, where the vulnerability is fully patched. Until upgrade is possible, restrict network access to the dagu web interface using firewalls or VPNs to limit exposure to trusted users only. Implement strict authentication and authorization controls to minimize the risk of unauthorized access. Conduct a thorough audit of existing DAG files and related directories to detect any unauthorized modifications or suspicious activity. Monitor logs for unusual API requests containing encoded path traversal sequences such as %2F. Employ web application firewalls (WAFs) with custom rules to detect and block path traversal attempts targeting the {fileName} parameter. Educate administrators and developers about secure coding practices, emphasizing consistent input validation across all API endpoints. Finally, integrate vulnerability scanning and penetration testing into the development lifecycle to detect similar issues proactively.

Description

CVE-2026-33344 is a high-severity path traversal vulnerability in the dagu workflow engine versions 2.0.0 up to but not including 2.3.1. The flaw arises because several API endpoints (GET, DELETE, RENAME, EXECUTE) fail to properly validate the {fileName} URL parameter, allowing attackers to use encoded forward slashes (%2F) to traverse directories outside the intended DAGs directory. This can lead to unauthorized access and modification of files, impacting confidentiality and integrity. The vulnerability requires network access and low privileges but no user interaction. It was patched in version 2.3.

Impact

The vulnerability allows unauthorized directory traversal, enabling attackers to access, modify, or execute files outside the intended DAGs directory. This can lead to disclosure of sensitive information, tampering with workflow definitions, or execution of arbitrary code if executable files are accessible. For organizations relying on dagu for workflow automation, this could disrupt business processes, cause data breaches, or facilitate further compromise of internal systems. Since the vulnerability requires only low privileges and no user interaction, it can be exploited remotely by authenticated users or potentially by attackers who gain limited access. The impact is particularly severe in environments where dagu is exposed to untrusted networks or integrated with critical infrastructure. The lack of known exploits in the wild suggests limited active exploitation so far, but the high CVSS score and straightforward exploitation method indicate a strong potential for damage if left unpatched.

CWE-22Improper Limitation of a Pathname to a Restricted Directory (Path Traversal) (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #6OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
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.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
Architecture and Design
For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks…
Implementation · Input Validation
Inputs should be decoded and canonicalized to the application's current internal representation before being validated (CWE-180). Make sure that the application does not decode the same input twice (CWE-174).
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V12.3.1 (opens in a new tab)
Attack patterns
Path Traversal (opens in a new tab)
Using Slashes and URL Encoding Combined to Bypass Validation Logic (opens in a new tab)
Manipulating Web Input to File System Calls (opens in a new tab)
Using Escaped Slashes in Alternate Encoding (opens in a new tab)
Using Slashes in Alternate Encoding (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 31 Mar 2026, 20:34 UTC

WeaknessesCWE-22

Technical details

References

Community reviews

Related threats