The vulnerability allows attackers who can authenticate with a viewer‑role API key to supply absolute or relative paths that bypass file‑containment restrictions, enabling reading of any .yaml or .yml files accessible to the Dagu process. This creates a direct confidentiality risk: sensitive configuration or secret files can be disclosed by simply sending a crafted request to the DAG specification API. No write or execution permissions are granted by the affected operation, so the threat is limited to information disclosure rather than full system compromise.

All installations of the Dagu workflow engine running a version earlier than 2.11.0 are susceptible. The product is provided by DaguCloud under the dagu name. The issue is resolved in the 2.11.0 release and later.

With a CVSS score of 6.5, the vulnerability is considered moderate severity but still significant due to the ease of exploitation: an attacker only needs an authenticated viewer‑role API key, which may be routinely distributed. The EPSS score is not available, and the vulnerability is not yet listed in CISA's KEV catalog, yet the lack of operand restrictions means the attack can succeed in any environment where the Dagu process has file system access. Because the flaw permits reading outside the configured DAG directories, it can expose data that otherwise would remain protected by the application’s isolation rules.