External risk intelligence

Dokploy Authenticated Command Injection Vulnerability.

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-72902

Dokploy is a self-hostable Platform as a Service (PaaS) designed for managing deployments. As a central management interface for applications and infrastructure, it is commonly deployed as an internet-facing service or web portal to facilitate remote access and management, making its interface and associated API endpoints frequently exposed to the network.

OS Command Injection

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

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

A vulnerability in Dokploy, a self-hosted Platform as a Service, could allow an authenticated user to run unauthorized commands on connected servers. This impacts systems that manage application deployments. The main concern is confirming relevance and exposure to Dokploy instances.

  • Unauthenticated users can run commands on servers.
  • Critical systems for application deployment are affected.
  • Confirm Dokploy use and exposure is the priority.

Attack Path

How an attacker could exploit the issue

An authenticated user could leverage this vulnerability by interacting with the registry functions within Dokploy. When adding or managing registry credentials, the application improperly handles the password field, directly embedding it into a shell command. This allows an attacker to execute arbitrary commands on the server hosting Dokploy or any server managed via SSH.

  • Requires authenticated access.
  • Interpolates password into shell command.
  • Allows arbitrary command execution.

Live Threat

Current exploitation, exposure, and threat context

An authenticated user could execute arbitrary commands on a server connected to Dokploy. This occurs when the password field is directly used in a shell command, potentially affecting the integrity and availability of the target system.

  • Server command execution on target.
  • Authenticated user interpolates password.
  • System compromise and data loss.

Operational Fix

Recommended remediation, mitigation, and detection steps

Real-World Ownership:

Teams responsible for managing Dokploy deployments, likely infrastructure or platform engineering, should first confirm the presence and scope of this PaaS within their environment. Once identified, these teams must assess the reachability and criticality of affected Dokploy instances to prioritize remediation efforts and engage the accountable owner.

  • Platform or infrastructure teams own the issue.
  • Verify Dokploy instance reachability and 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 Dokploy?

Dokploy is an open-source, self-hosted Platform as a Service (PaaS). It serves as a management hub that simplifies how developers deploy applications and manage infrastructure, including SSH-connected target servers, through a centralized web-based dashboard.

What is the CVE-2026-72902 vulnerability?

This is a command injection vulnerability (CWE-78). It occurs because the software insecurely processes user input in the registry configuration settings. Instead of safely handling credentials, the application improperly embeds the password field directly into a system shell command, allowing unauthorized code execution.

How is CVE-2026-72902 triggered?

An attacker triggers this by providing malicious input within the registry management functions of the Dokploy interface. Importantly, this requires an authenticated account; anonymous, unauthenticated visitors cannot trigger the command injection.

Is my Dokploy instance at risk?

According to Halo Surface Signal, Dokploy is often deployed as an internet-facing service or web portal to enable remote management. Because the API endpoints are frequently exposed to the network, instances accessible from the internet face a higher likelihood of being reachable by potential attackers.

What should I do to address this issue?

If you are responsible for managing a Dokploy deployment, your first step is to verify the version currently in use. You should promptly update to version 0.29.13 or later, which resolves the insecure command handling, and confirm that all managed infrastructure is secured.

References