GHSA-6QR9-G2XW-CW92

Dagu's default configuration ships with authentication disabled. The POST /api/v2/dag-runs endpoint accepts an inline YAML spec and executes its shell commands immediately with no credentials required, any dagu instance reachable over the network is fully compromised by default.

Details

internal/service/app/config/loader.go:226 sets AuthModeNone as the default. With no auth mode configured, internal/frontend/api/v2/handlers/api.go:520 returns nil from requireExecute(), all permission checks pass without a valid session.

The POST /api/v2/dag-runs endpoint accepts a spec field containing a full YAML DAG definition. The spec is parsed and the commands execute immediately on the host with no validation beyond YAML parsing.

PoC

curl -s -X POST http://TARGET:8080/api/v2/dag-runs \
  -H "Content-Type: application/json" \
  -d '{"name":"poc","spec":"steps:\n  - name: rce\n    command: id > /tmp/pwned\n"}'
# Response: {"dagRunId":"<uuid>"}
# /tmp/pwned contains: uid=1000(dagu) gid=1000(dagu)

Confirmed on ghcr.io/dagu-org/dagu:latest with no configuration changes.

Every dagu deployment using default settings, every Docker deployment, every install following the documentation, every instance without explicit DAGU_AUTH_MODE configuration, is fully compromised without credentials. An attacker with network access gets OS command execution as the dagu process user.

A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.

GHSA-6QR9-G2XW-CW92 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Kodem intelligence

1. What is GHSA-6QR9-G2XW-CW92? GHSA-6QR9-G2XW-CW92 is a critical-severity missing authentication for critical function vulnerability in github.com/dagu-org/dagu (go), affecting versions <= 1.30.3. No fixed version is listed yet. A critical operation is accessible without requiring any authentication.
2. How severe is GHSA-6QR9-G2XW-CW92? GHSA-6QR9-G2XW-CW92 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/dagu-org/dagu are affected by GHSA-6QR9-G2XW-CW92? github.com/dagu-org/dagu (go) versions <= 1.30.3 is affected.
4. Is there a fix for GHSA-6QR9-G2XW-CW92? No fixed version is listed for GHSA-6QR9-G2XW-CW92 yet. Monitor the advisory for updates and apply mitigations in the interim.
5. Is GHSA-6QR9-G2XW-CW92 exploitable, and should I be worried? Whether GHSA-6QR9-G2XW-CW92 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether GHSA-6QR9-G2XW-CW92 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix GHSA-6QR9-G2XW-CW92? No fixed version is listed yet. In the interim: Keep the dependency up to date. Add authentication gating to all sensitive endpoints.