Description

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, the compose.update operation stores an unvalidated composePath that packages/server/src/utils/builders/compose.ts and packages/server/src/services/compose.ts interpolate into docker compose -f, docker stack deploy -c, and touch shell commands executed through /bin/sh -c. An authenticated member with compose write and deploy permission can supply a crafted composePath, trigger compose.deploy or startCompose, and execute arbitrary operating-system commands in the Docker-privileged Dokploy host context. This issue is fixed in version 0.29.13.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "9.9",
  "pubDate": "2026-08-10T19:17:35.160Z",
  "pubdate": "2026-08-10T19:17:35.160Z",
  "executiveSummary": "A command injection vulnerability exists in Dokploy prior to version 0.29.13 within the compose.update operation. The flaw arises from the insecure handling of the unvalidated composePath parameter, which is directly interpolated into shell commands executed via /bin/sh -c.\nAn authenticated attacker with compose write and deploy permissions can supply a specially crafted composePath string and subsequently trigger the compose.deploy or startCompose functions. This execution flow results in arbitrary operating-system command execution directly within the context of the Docker-privileged Dokploy host.\nThe impact of this vulnerability is critical, as successful exploitation grants the attacker full administrative control over the host operating system through privileged container infrastructure. The vulnerability specifically affects Dokploy versions prior to 0.29.13 and requires authenticated access with specific authorization roles.\nRemediation requires upgrading Dokploy to version 0.29.13 or later, where input validation for compose paths is properly enforced to prevent shell command injection.",
  "technicalDetails": "The root cause of the vulnerability is improper input validation and unsafe command construction within the application logic. Specifically, the compose.update operation stores an unvalidated composePath parameter without sanitization or escaping mechanisms.\nThe vulnerable components include packages/server/src/utils/builders/compose.ts and packages/server/src/services/compose.ts. These modules take the unvalidated composePath value and interpolate it directly into underlying shell commands, including docker compose -f, docker stack deploy -c, and touch, which are then spawned and executed via the /bin/sh -c shell interpreter.\nExploitation requires an attacker to possess authentication credentials along with specific authorization: compose write and deploy permissions. With these capabilities, the attack flow proceeds as follows: First, the attacker sends a request to the compose.update endpoint containing a maliciously crafted payload within the composePath parameter, such as shell metacharacters designed to break out of the intended argument context. Second, the attacker invokes either the compose.deploy or startCompose functions.\nUpon invocation, the backend service reads the malicious composePath and interpolates it directly into the command string executed by /bin/sh -c. The underlying shell interprets the injected characters, allowing the attacker to break out of the intended binary arguments and execute arbitrary operating-system commands.\nBecause Dokploy operates within a Docker-privileged host context, the execution of arbitrary operating-system commands leads to complete system compromise, enabling the attacker to escape container boundaries or subvert host infrastructure depending on the deployment configuration. The issue is fully remediated in version 0.29.13."
}