# CVE-2026-33344: Dagu has an incomplete fix for CVE-2026-27598: path traversal via %2F-encoded slashes in locateDAG

> Attackers can traverse directories via encoded slashes in API endpoints to read or modify files outside the intended DAG directory.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Mar 2026
- **Updated:** 24 Mar 2026
- **Also known as:** GHSA-ph8x-4jfv-v9v8, GO-2026-4785

## What is CVE-2026-33344?

CVE-2026-33344 is a high-severity path traversal vulnerability in dagu-org dagu, published on 24 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-33344?

3 open source packages ship an affected version, including github.com/dagu-org/dagu. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/dagu-org/dagu` | Go | From 1.30.4-0.20260221021317-e2ed589105d7 | 1.30.4-0.20260319093346-7d07fda8f9de |
| `github.com/dagu-org/dagu` | Go | From 1.30.4-0.20260221021317-e2ed589105d7 | 1.30.4-0.20260319093346-7d07fda8f9de |
| `github.com/dagu-org/dagu` | Go | From 1.30.4-0.20260221021317-e2ed589105d7 | 1.30.4-0.20260319093346-7d07fda8f9de |

Products: Dagu Dagu.

## How do I fix CVE-2026-33344?

Upgrade github.com/dagu-org/dagu to 1.30.4-0.20260319093346-7d07fda8f9de or later.

## Is CVE-2026-33344 being exploited?

There is no known exploitation of CVE-2026-33344 in the wild and no public exploit code.

## Other vulnerabilities in dagu-org dagu

- [CVE-2026-31886](https://insights.sbomify.com/CVE-2026-31886/): Dagu has a Path Traversal via `dagRunId` in Inline DAG Execution (critical 9.1)
- [CVE-2026-31882](https://insights.sbomify.com/CVE-2026-31882/): Dagu SSE Authentication Bypass in Basic Auth Mode (high 7.5)
- [CVE-2026-27598](https://insights.sbomify.com/CVE-2026-27598/): Dagu: Path traversal in DAG creation allows arbitrary YAML file write outside DAGs directory (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-33344 and fix it if it is affected.

What it is: CVE-2026-33344 is a high-severity path traversal vulnerability in dagu-org dagu, published on 24 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-33344 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/dagu-org/dagu (Go): affected from 1.30.4-0.20260221021317-e2ed589105d7; fixed in 1.30.4-0.20260319093346-7d07fda8f9de
- github.com/dagu-org/dagu (Go): affected from 1.30.4-0.20260221021317-e2ed589105d7; fixed in 1.30.4-0.20260319093346-7d07fda8f9de
- github.com/dagu-org/dagu (Go): affected from 1.30.4-0.20260221021317-e2ed589105d7; fixed in 1.30.4-0.20260319093346-7d07fda8f9de

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-33344/ (Markdown: https://insights.sbomify.com/CVE-2026-33344/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-33344
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-33344
- OSV: https://osv.dev/vulnerability/CVE-2026-33344

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-33344/
Summaries are generated and may contain mistakes; the official description above is the record.