Description

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, the mariadb.ts, mongo.ts, mysql.ts, postgres.ts, redis.ts, and libsql.ts Dokploy database service deployment functions pass user-controlled dockerImage fields unquoted into docker pull ${dockerImage} shell commands on the remote-server code path. This vulnerability is fixed in 0.29.13.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "9.9",
  "pubDate": "2026-08-10T18:18:53.047Z",
  "pubdate": "2026-08-10T18:18:53.047Z",
  "executiveSummary": "A command injection vulnerability exists within the Dokploy platform prior to version 0.29.13.\nThe vulnerability affects multiple database service deployment functions, specifically mariadb.ts, mongo.ts, mysql.ts, postgres.ts, redis.ts, and libsql.ts.\nThe root cause stems from the insecure handling of user-controlled dockerImage fields, which are passed unquoted directly into underlying shell execution contexts when running docker pull ${dockerImage} commands on the remote-server code path.\nAn authenticated or otherwise capable attacker who can supply a manipulated dockerImage value can inject arbitrary shell commands, leading to remote code execution on the underlying host or remote server.\nThe impact includes full compromise of the affected server infrastructure hosting the Dokploy deployment.\nThis vulnerability is resolved in version 0.29.13 by properly sanitizing or quoting user-supplied input before execution in shell commands.",
  "technicalDetails": "The vulnerability resides in the database service deployment modules of Dokploy, specifically within the following files: mariadb.ts, mongo.ts, mysql.ts, postgres.ts, redis.ts, and libsql.ts.\nDuring the database service deployment workflow on the remote-server code path, the application constructs a shell command utilizing template literals to execute a docker pull operation.\nThe user-controlled dockerImage input parameter is concatenated directly into the shell command string without adequate quotation, escaping, or validation, forming an instruction similar to docker pull ${dockerImage}.\nAn attacker can exploit this behavior by providing a maliciously crafted payload within the dockerImage field containing shell metacharacters (such as semicolons, backticks, or pipe symbols) followed by arbitrary system commands.\nWhen the application executes the resulting string via its shell execution mechanism, the operating system shell interprets the injected metacharacters and executes the attacker's payload with the privileges of the running Dokploy service or remote agent.\nAffected software versions include all Dokploy installations prior to 0.29.13.\nThe attack vector requires the ability to supply or modify the dockerImage parameter within the database deployment configuration functionality.\nPost-exploitation impact allows the execution of arbitrary commands on the remote server, potentially compromising all hosted services, containers, and underlying infrastructure."
}