Description

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, Dokploy passes user-controlled values directly into shell commands via unquoted template literal interpolation in the registry credential testing and Docker Swarm cluster management endbpoints. Both endpoints have a safe local code path (using execFileAsync or the Docker API) but a vulnerable remote path (using execAsyncRemote which runs the shell string via SSH). This vulnerability is fixed in 0.29.13.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "9.9",
  "pubDate": "2026-08-10T18:18:52.123Z",
  "pubdate": "2026-08-10T18:18:52.123Z",
  "executiveSummary": "Dokploy prior to version 0.29.13 is affected by an OS command injection vulnerability involving unquoted template literal interpolation within registry credential testing and Docker Swarm cluster management endpoints.\nThe vulnerability allows remote attackers with access to the affected endpoints to pass arbitrary user-controlled values directly into shell execution routines when interacting with remote targets via SSH.\nSuccessful exploitation of this vulnerability leads to arbitrary remote code execution on the underlying operating system with the privileges of the application process.\nThe flaw stems from inconsistent validation and insecure execution routing, where safe local execution functions are bypassed in favor of remote execution wrappers that execute raw shell strings.\nRisk implications are severe, potentially compromising the integrity, confidentiality, and availability of the self-hosted Platform as a Service environment and any connected managed nodes.\nRemediation requires upgrading Dokploy to version 0.29.13 or later, where proper input sanitization and secure execution boundaries have been implemented.",
  "technicalDetails": "The vulnerability resides in specific functional components of Dokploy prior to version 0.29.13, specifically within the registry credential testing and Docker Swarm cluster management endpoints.\nThe root cause is the improper neutralization of special elements used in operating system commands, implemented via unquoted template literal interpolation of user-supplied parameters directly into shell command strings.\nDokploy features dual code paths for executing operations: a local code path that securely utilizes execFileAsync or direct API interfaces such as the Docker API, and a remote code path that utilizes execAsyncRemote.\nWhen processing requests targeting remote environments, the application invokes execAsyncRemote, which executes the constructed shell string over an SSH connection without sufficient validation or escaping of input variables.\nAn attacker can exploit this flaw by supplying specially crafted inputs containing shell metacharacters through the vulnerable registry credential testing or Docker Swarm cluster management interfaces.\nDuring the attack flow, the malicious payload is interpolated directly into the command string sent to the remote execution wrapper, causing the underlying shell to interpret the injected characters as command separators or arguments.\nThis execution flow results in arbitrary command injection, enabling the attacker to execute arbitrary system commands on the remote target.\nThe affected component handles remote management tasks, requiring network exposure of the administrative or API endpoints utilized for cluster and registry configurations.\nDepending on the specific endpoint configuration, exploitation may require authentication or specific privilege levels associated with administrative or management functions within the Platform as a Service architecture.\nPost-exploitation impact includes full system compromise, lateral movement within connected cluster nodes, data exfiltration, and disruption of managed containerized workloads."
}