External risk intelligence

Dagu Unauthenticated OS Command Execution Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.3)

CVE-2026-126752

The vulnerability exists in an API endpoint (/api/v2/dag-runs) of a web-based application (Dagu) and is exploitable without authentication. Because the application facilitates workflow and task orchestration, it is commonly deployed as a network-accessible service, and the lack of default authentication makes this internet-facing API endpoint highly exposed to unauthorized remote access.

Missing Authentication

Halo Surface Signal: 5 out of 5 — more likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory addresses a critical vulnerability in Dagu, a workflow and task orchestration tool, where an unauthenticated attacker can execute arbitrary operating system commands through a specific API endpoint. This is a significant concern as it allows for remote code execution on affected systems without any prior access.

  • Issue: Unauthenticated attackers can run commands remotely.
  • Why remember: Critical vulnerability, potentially wide impact.
  • Executive takeaway: Confirm relevance and assess exposure.

Attack Path

How an attacker could exploit the issue

An attacker can trigger this vulnerability by sending a specially crafted POST request to the `/api/v2/dag-runs` endpoint. This request can contain inline specifications that execute arbitrary operating system commands. Successful exploitation allows an unauthenticated attacker to achieve remote code execution on the affected system.

  • No authentication required.
  • Triggered via API POST request.
  • Remote code execution risk.

Live Threat

Current exploitation, exposure, and threat context

When supported by the advisory, unauthenticated attackers could execute arbitrary operating system commands by sending specially crafted POST requests to the `/api/v2/dag-runs` endpoint. This could lead to remote code execution, impacting the integrity and availability of the affected system.

  • System data could be compromised.
  • Commands sent via API endpoint.
  • Remote code execution on the system.

Operational Fix

Recommended remediation, mitigation, and detection steps

Application owners are likely responsible for this workflow orchestration tool, with infrastructure or platform teams supporting its deployment and network/security teams managing access. The initial step is to identify all instances of the affected technology, confirm their network exposure and business criticality, and locate the accountable owner to prioritize remediation.

  • Confirm application ownership and deployment scope.
  • Verify network exposure and business criticality.
  • Plan remediation based on identified risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is Dagu and why is it used?

Dagu is a workflow and task orchestration tool designed to automate complex sequences of operations. Engineers use it to manage, schedule, and execute data pipelines or routine background tasks across their infrastructure. Because it coordinates these processes, it is typically deployed as a central service that interacts with various system components to ensure tasks run as planned.

How does CVE-2026-126752 cause a security risk?

This vulnerability is classified as Missing Authentication for Critical Function (CWE-306). In affected versions, the software defaults its authentication mode to none. This oversight means the system does not verify who is making requests, allowing unauthenticated users to interact with sensitive API functions that should be protected.

What triggers the vulnerability in Dagu?

The flaw is triggered when an attacker sends a specially crafted POST request to the /api/v2/dag-runs endpoint. This request includes an inline specification containing arbitrary shell commands, which the system then executes. Importantly, requests that do not target this specific endpoint or fail to include the malicious command payload do not trigger this remote code execution path.

Do I need to worry if my Dagu instance is internal?

According to Halo Surface Signal, this vulnerability is particularly dangerous because Dagu is a web-based service often deployed in network-accessible environments. While an internet-facing instance is at the highest risk, internal instances are still vulnerable to anyone with network access to the server. You should assume any instance reachable by unauthorized users is at risk.

What is the first step to address this CVE?

You should begin by creating a comprehensive inventory of all Dagu instances running in your environment. Once identified, verify their specific version to see if they fall within the affected range. After mapping your deployments, work with the designated application owners to prioritize upgrading your installations to a secure version that mandates proper authentication.

References