External risk intelligence

Dokploy Destination Command Injection Vulnerability

CVE advisorySeverity: CRITICAL (CVSS 9.9)

CVE-2026-72868

Dokploy is a self-hostable Platform as a Service (PaaS) designed to manage application deployments. Such systems typically operate as internet-facing management consoles or centralized orchestration portals to facilitate remote service administration and deployment, making the interface and its associated APIs commonly accessible in network-connected environments.

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 critical vulnerability has been identified in Dokploy, a self-hosted Platform as a Service, which could allow unauthorized command execution. This issue stems from how sensitive credentials are handled when testing connections to storage destinations. If exploited, an attacker could gain control over the Dokploy container, potentially impacting the host system.

  • Unauthorized commands can be run on Dokploy.
  • It impacts systems managing application deployments.
  • Confirm if Dokploy is in use and affected.

Attack Path

How an attacker could exploit the issue

An attacker with low-level access to an organization within Dokploy can exploit a vulnerability in the destination connection test feature. By providing specially crafted input, they can trick the system into executing arbitrary commands on the server. This could allow them to gain control of the host system, potentially impacting the Docker environment.

  • Requires low-privileged member access.
  • Triggers when testing destination connection.
  • Leads to arbitrary command execution.

Live Threat

Current exploitation, exposure, and threat context

A low-privileged organization member could exploit this vulnerability to execute arbitrary commands within the Dokploy container. This could impact the confidentiality, integrity, and availability of the Dokploy system and potentially the host environment when supported by the advisory.

  • Containerized application deployment configurations.
  • Unauthenticated, low-privileged access to execute commands.
  • Compromise of container and host Docker socket.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability affects self-hosted Dokploy installations. The primary responsibility for addressing this issue likely falls to the infrastructure or platform team managing Dokploy, with coordination from the security team to assess exposure and from vendor management if a managed service is in place. The first practical step is to identify all Dokploy instances, confirm their accessibility and criticality, and then engage the accountable owner to plan remediation, which may involve vendor coordination if updates are managed externally.

  • Infrastructure/Platform team ownership.
  • Verify Dokploy instance exposure and criticality.
  • Plan remediation and coordinate vendor updates.

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 a self-hostable Platform as a Service (PaaS) that simplifies managing application deployments. Users leverage it to automate the delivery of their software, often acting as a centralized orchestration portal. Because it handles various deployment configurations and storage destinations, it functions as a management console that coordinates how applications interact with underlying server infrastructure.

What is the vulnerability in CVE-2026-72868?

This vulnerability is a form of OS Command Injection, classified as CWE-78. It occurs when the software takes user-provided input and inserts it directly into a system command without sufficient validation. Because the application combines this input with administrative connection settings, an attacker can escape the intended command structure and force the server to execute unintended, malicious code.

How does an attacker trigger this command injection?

The flaw is triggered when a user initiates a destination connection test within the application. An attacker with low-privileged account access provides crafted input into specific fields, such as the bucket or endpoint name. This action does not occur automatically; it requires the user to interact with the connection testing feature. Simple, non-malicious inputs used for standard configuration will not trigger the vulnerability.

Is my Dokploy instance at risk?

If you run a version prior to 0.29.13, your instance is susceptible. According to Halo Surface Signal, Dokploy instances typically serve as internet-facing management consoles to facilitate remote administration, which increases the likelihood of visibility to unauthorized actors. Organizations should prioritize assessing any instance that is reachable over the network, as the vulnerability allows for significant escalation.

How do I secure my environment against this issue?

The primary step is to update your Dokploy installation to version 0.29.13 or later, which contains the necessary security fixes. Before applying the update, verify all your running instances to determine which are active and assess their network accessibility. If you cannot update immediately, restrict access to the management interface to trusted users only to prevent unauthorized members from reaching the vulnerable function.

References