Dokploy versions prior to 0.29.13 build shell commands by concatenating user‑supplied compose service names and configuration into bash strings. The implementation fails to escape or validate the data, allowing a deployer to insert shell metacharacters. When a malicious compose file is deployed, the injected characters are processed by the host shell, giving the attacker arbitrary command execution on the Docker host. This is an OS command injection flaw that could lead to full system compromise, allowing an attacker to read, modify, or delete any data accessible to the host and to install persistent backdoors.

Vulnerable builds include all Dokploy releases before 0.29.13, such as 0.29.12 and earlier. The affected component is the compose command‑generation logic in the createCommand() function in the Dokploy source code. The fix was released in the 0.29.13 tag. Operators using earlier versions must upgrade to a patched release to eliminate this flaw.

The CVSS score of 6.5 indicates a medium‑severity risk. The EPSS score is not available, so the probability of exploitation is unknown. The vulnerability is not listed in CISA’s KEV catalog. Exploitation requires the ability to deploy a compose file with a crafted service name or definition; therefore users with deployment privileges could abuse it. Once a malicious compose is deployed, commands run with the privileges of the Docker host user, potentially providing full administrative control. The issue is mitigated by applying the 0.29.13 patch. Until patched, the exposure remains while users can still deploy arbitrary compose files.