Description

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, the createCommand() function constructs shell commands by interpolating compose service names and configuration into bash command strings. When a compose with a maliciously crafted name or service definition is deployed, the shell metacharacters are interpreted as command separators, allowing arbitrary command execution on the Docker host. This vulnerability is fixed in 0.29.13.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "6.5",
  "pubDate": "2026-08-10T18:18:52.577Z",
  "pubdate": "2026-08-10T18:18:52.577Z",
  "executiveSummary": "An arbitrary command execution vulnerability exists in Dokploy prior to version 0.29.13 within the createCommand() function. The vulnerability arises from insecure string interpolation of Docker Compose service names and configurations directly into bash command strings. When an attacker deploys a maliciously crafted compose configuration containing specific shell metacharacters, the underlying shell interprets these characters as command separators. This flaw enables unauthenticated or authenticated attackers with deployment privileges to execute arbitrary commands directly on the host operating system with the privileges of the Dokploy service. Successful exploitation leads to full system compromise, data exfiltration, and potential lateral movement within the infrastructure hosting the Docker daemon. The risk implication is critical, as complete administrative control of the Docker host can be achieved via untrusted compose deployments.",
  "technicalDetails": "The vulnerability resides in the createCommand() function within Dokploy prior to version 0.29.13. The root cause of the security issue is improper input validation and the unsafe construction of operating system shell commands. Instead of utilizing parameterized execution methods or safely escaping input arrays, the application concatenates user-supplied Docker Compose service names and configuration properties directly into raw bash command strings.\nThe exploitation method relies on injecting shell metacharacters, such as semicolons, ampersands, or backticks, into the compose service name or definition fields. When a user or automated process triggers the deployment of this malicious compose file, the vulnerable createCommand() function processes the input and passes the resulting unsanitized string to the underlying shell interpreter.\nThe attack flow proceeds as follows: First, the attacker crafts a malicious Docker Compose file where a service name or configuration attribute incorporates bash metacharacters followed by the desired operating system command payload. Second, the attacker initiates a deployment operation within Dokploy. Third, Dokploy reads the malicious configuration and invokes the createCommand() function, which interpolates the malicious payload into the command string. Fourth, the shell parses the resulting string, executes the injected metacharacters, and runs the attacker's arbitrary payload on the Docker host.\nThe affected component is the command generation logic handling Docker Compose deployments. Affected versions include all Dokploy installations prior to 0.29.13. The vulnerability requires the ability to deploy a compose file within the platform. Payload behavior includes executing arbitrary system binaries, modifying host files, or establishing reverse shells. Post-exploitation impact encompasses total host compromise, container escape scenarios, and persistent unauthorized access to the underlying infrastructure."
}