Skip to main content
Menu
CVEs

CVE

Dagu unauthenticated remote code execution in dag-runs API

Affects Dagu 1.23.0 before 2.0.0 in its default configuration, where authentication is disabled. Fixed in 2.0.0.

CVE-2026-126752Published Updated Summary written by a model

9.3CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
Fixed in 2.0.0
Who is exposed
Default setups

Do first: Check every install: default setups are affected.

Summary

Dagu 1.23.0 before 2.0.0 defaults auth.mode to none, allowing unauthenticated attackers to execute OS commands through the /api/v2/dag-runs endpoint. Attackers can send a POST request with an inline spec defining steps containing arbitrary shell commands to achieve remote code execution. Exploitation evidence was first observed by the Shadowserver Foundation on 2026-03-11.

Who should check

Teams running Dagu with default auth settings (auth mode none) where the API is reachable over the network, including Docker deployments, plus anyone running Dagu <= 1.30.3.

“Dagu's default configuration ships with authentication disabled.”

github.com

cve.now Index

50Pcve.now Index 50 of 100 · methodology v3 · provisional
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure25/25Default setups, CISA rates it automatable
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.3, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 75 if added to CISA KEV
  • Would score about 70 if CISA's SSVC rates exploitation active

What to do

  • Check every install: default setups are affected.

  • Upgrade to a fixed version: 2.0.0.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-126752 (Dagu 1.23.0 < 2.0.0 Unauthenticated RCE via /api/v2/dag-runs), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126752 (entry last updated 2026-11-18):
Affected:
- dagu-org Dagu: from 1.23.0, fixed in 2.0.0
Fixed versions: 2.0.0.
Conditions (all must be true for the bug to be hit):
- Dagu runs with its default configuration (auth mode none, authentication disabled) (source: https://github.com/dagucloud/dagu/security/advisories/GHSA-6qr9-g2xw-cw92)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-126752 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126752 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/dagucloud/dagu/security/advisories/GHSA-6qr9-g2xw-cw92
- https://github.com/dagucloud/dagu/pull/1688
- https://github.com/dagucloud/dagu/commit/c0e7cf7e1cfc3a52af8a9fb2da1ca911a9958649
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/vulnerabilities/other/dagu-rce.yaml
- https://www.vulncheck.com/advisories/dagu-1.23.0-before-2.0.0-unauthenticated-rce-via-api-v2-dag-runs
- https://www.vulncheck.com/advisories/dagu-1.23.0-2.0.0-unauthenticated-rce-via-api-v2-dag-runs
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126752
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126752"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: poc · Automatable: yes · Technical impact: total

  5. Record last updated

Affected versions

  • dagu-org Dagu

    From 1.23.0 · fixed in 2.0.0

Evidence 8

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-126752

Is CVE-2026-126752 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

An attacker with network access can POST an inline YAML spec to the Dagu API and get OS command execution as the dagu process user, without logging in.Source: github.com

Which versions are affected by CVE-2026-126752?

Dagu: from 1.23.0 before 2.0.0.Source: cve.now feed data

Am I affected, and how do I check?

Dagu versions from 1.23.0 up to but not including 2.0.0 are in range. The default configuration ships with authentication disabled (auth mode none), so check the auth mode setting in the Dagu configuration to see how the instance is set up.Source: github.com

How do I fix CVE-2026-126752?

Upgrade Dagu to 2.0.0 or later, which is the fixed version listed for this range.Source: github.com

More CVEs