CVE-2026-27598: Dagu: Path traversal in DAG creation allows arbitrary YAML file write outside DAGs directory

Published Feb 24, 2026
·
Updated

Dagu is a workflow engine with a built-in Web user interface. In versions up to and including 1.16.7, the CreateNewDAG API endpoint (POST /api/v1/dags) does not validate the DAG name before passing it to the file store. An authenticated user with DAG write permissions can write arbitrary YAML files anywhere on the filesystem (limited by the process permissions). Since dagu executes DAG files as shell commands, writing a malicious DAG to the DAGs directory of another instance or overwriting config files can lead to remote code execution. Commit e2ed589105d79273e4e6ac8eb31525f765bb3ce4 fixes the issue.

Other sources

The CreateNewDAG API endpoint (POST /api/v1/dags) does not validate the DAG name before passing it to the file store. While RenameDAG calls core.ValidateDAGName() to reject names containing path separators (line 273 in dags.go), CreateNewDAG skips this validation entirely and passes user input directly to dagStore.Create().

In internal/persis/filedag/store.go, the generateFilePath function (line 493) checks if the name contains a path separator, and if so, resolves it via filepath.Abs(name) — completely ignoring the baseDir. This means a name like ../../tmp/pwned will write a file to /tmp/pwned.yaml instead of the DAGs directory.

Affected code:

internal/service/frontend/api/v1/dags.go line 120-170 — CreateNewDAG handler, no call to ValidateDAGName

internal/persis/filedag/store.go line 493-498 — generateFilePath resolves absolute path when name contains separator

internal/persis/filedag/store.go line 213 — Create calls generateFilePath and writes attacker-controlled YAML content to the resolved path

PoC:

curl -X POST http://localhost:8080/api/v1/dags \ -H "Content-Type: application/json" \ -d '{ "name": "../../tmp/path-traversal-proof", "spec": "steps:\n - command: id > /tmp/pwned\n" }'

After this request, a file /tmp/path-traversal-proof.yaml will be created with the attacker-supplied content. The file will be written with the permissions of the dagu process.

An authenticated user with DAG write permissions can write arbitrary YAML files anywhere on the filesystem (limited by the process permissions). Since dagu executes DAG files as shell commands, writing a malicious DAG to the DAGs directory of another instance or overwriting config files can lead to remote code execution.

— GitHub

Affected Software

2 affected components
go/github.com/dagu-org/dagu<=1.16.7
Dagu Dagu<=1.16.7

Event History

Feb 24, 2026
Advisory Published
via GitHub·09:43 PM
Data Sourced
via GitHub·09:43 PM
DescriptionWeaknessAffected Software
Feb 25, 2026
CVE Published
via MITRE·12:27 AM
Data Sourced
via MITRE·12:27 AM
DescriptionWeakness
Data Sourced
via NVD·01:16 AM
RemedyDescriptionSeverityWeaknessAffected Software
Oct 1, 58139
Event
via FIRST·12:21 PM

Frequently Asked Questions

1

What is the severity of CVE-2026-27598?

CVE-2026-27598 has a medium severity rating due to the potential for arbitrary file write vulnerabilities.

2

How do I fix CVE-2026-27598?

To fix CVE-2026-27598, update the Dagu workflow engine to version 1.16.8 or later, which includes a patch for the vulnerability.

3

What versions of Dagu are affected by CVE-2026-27598?

CVE-2026-27598 affects Dagu versions up to and including 1.16.7.

4

What is the exploit vector for CVE-2026-27598?

The exploit vector for CVE-2026-27598 is the `CreateNewDAG` API endpoint which allows path traversal.

5

Can CVE-2026-27598 lead to severe system compromise?

While CVE-2026-27598 allows arbitrary file write, the severity of the impact depends on the permissions and configurations of the server.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203