Dagu MCP DAG specification read bypasses path containment and workspace isolation
- Exploited
- No known exploitation
- Fix
- Fixed in 2.11.0
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.11.0.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 10/100 · provisional
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Dagu, a workflow engine with a built-in Web user interface, has a flaw in its MCP dagu_read operation that lets a remote attacker with a viewer-role API key read .yaml and .yml files outside the configured DAG directories. The attacker supplies an absolute or traversing path, and the operation cannot write or execute anything.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
Read the original description
Dagu is a workflow engine with a built-in Web user interface. Prior to version 2.11.0, its MCP dagu_read operation with target dag_spec invokes the DAG specification API directly, bypassing the HTTP middleware introduced for CVE-2026-33344. The underlying resolver does not restrict resolved paths to configured DAG directories. An authenticated attacker with a viewer-role API key can supply an absolute or traversing path to read .yaml or .yml files outside those directories that are accessible to the Dagu process. The affected operation does not provide write or execution capability. This issue is fixed in version 2.11.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.11.0.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- dagucloud dagu
fixed in 2.11.0
Evidence 4
- Advisory
- Repository
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-102943
Is CVE-2026-102943 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. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-102943?
dagu: before 2.11.0.Source: cve.now feed data
How do I fix CVE-2026-102943?
Upgrade to a fixed version: 2.11.0.Source: cve.now feed data