Dokploy: 25 Critical Command Injection and Auth Flaws Disclosed Together
Dokploy, a self-hostable PaaS, suffers from a critical batch of 25 vulnerabilities, primarily command injection flaws, patched in version 0.29.13.
Key findings
- 25 critical command injection and authorization flaws disclosed for Dokploy on August 10, 2026.
- Vulnerabilities affect versions prior to 0.29.13, with all fixed in 0.29.13.
- Flaws include improper input sanitization leading to arbitrary command execution.
- Authorization weaknesses allow unauthorized access to servers and data.
- Sensitive information like GitHub secrets and database credentials at risk.
- Urgent update to Dokploy 0.29.13 recommended for all users.
On August 10, 2026, a significant batch of 25 vulnerabilities was disclosed for Dokploy, a free, self-hostable Platform as a Service (PaaS). The vulnerabilities, all patched in version 0.29.13, predominantly involve critical command injection flaws, with many carrying a CVSSv3 score of 9.9. These issues stem from improper sanitization and interpolation of user-controlled input into shell commands across various components of the Dokploy application.
The vulnerabilities can be broadly categorized by the components and functions they affect:
Command Injection via User Input Interpolation
A large number of CVEs, including CVE-2026-72902, CVE-2026-72901, CVE-2026-72882, CVE-2026-72880, CVE-2026-72878, CVE-2026-72877, CVE-2026-72876, CVE-2026-72875, CVE-2026-72874, CVE-2026-72872, CVE-2026-72870, CVE-2026-72869, CVE-2026-72868, CVE-2026-72865, and CVE-2026-72864, are rooted in the improper handling of user-supplied data within shell command construction. For instance, CVE-2026-72902 and CVE-2026-72901 detail how interpolated password and volumeName fields, respectively, allow authenticated users to execute arbitrary commands. Similarly, CVE-2026-72882 highlights the injection of shell metacharacters into filePath for file mounts, leading to command execution over SSH. CVE-2026-72878 and CVE-2026-72877 demonstrate how user-controlled database fields and dockerImage values are directly interpolated into shell commands without proper quoting or validation, enabling command execution. CVE-2026-72869 and CVE-2026-72864 specifically point to issues in docker pull and docker compose commands, respectively, where unvalidated inputs lead to command injection. CVE-2026-72868 involves the interpolation of sensitive AWS S3 credentials into rclone ls commands.
Authorization and Access Control Flaws
Several vulnerabilities exploit weaknesses in authorization and access control mechanisms. CVE-2026-72886 describes how a member could bypass host-schedule gates by manipulating serviceId derivation. CVE-2026-72883 points to insufficient validation in WebSocket handlers for terminal and log streams, allowing unauthorized access to organization members' data. CVE-2026-72876 indicates that serverId could be accepted without proper ownership checks, potentially allowing access to another organization's server information. CVE-2026-72866 and CVE-2026-72864 highlight authorization issues related to terminal access and compose operations, where authenticated users could access unauthorized servers or execute commands on unintended targets. CVE-2026-72865 also involves insufficient authorization for docker-container-terminal access, allowing attackers to control arbitrary containers.
Path Traversal and File System Manipulation
Vulnerabilities related to path traversal and file system manipulation include CVE-2026-72885, where dockerContextPath is interpolated into an unquoted cd command, and CVE-2026-72875, where custom Git URLs and branches are interpolated into git clone commands, potentially leading to unintended file operations. CVE-2026-72884 notes that sanitizeCommand only trims whitespace and strips surrounding quotes, allowing command injection through crafted compose.command values. CVE-2026-72871, affecting the GitHub provider setup, trusts organizationId and userId from the state parameter without proper validation. CVE-2026-72867, an incomplete fix for a previous vulnerability, allows malicious Git branch names to be stored and used in shell commands.
Other Vulnerabilities
CVE-2026-72873 involves the leakage of sensitive GitHub secrets (githubClientSecret, githubPrivateKey, githubWebhookSecret) in API responses for application details. CVE-2026-72881 describes how database backup and restore commands embed database names, usernames, and passwords into shell commands, posing a risk if these credentials are not properly handled. CVE-2026-72879 details how registry passwords and URLs are interpolated directly into shell commands without escaping. CVE-2026-72884 points to insufficient sanitization of commands, allowing injection.
All 25 vulnerabilities were fixed in Dokploy version 0.29.13. Users are strongly advised to update to this version immediately to mitigate the risks associated with these critical command injection and authorization flaws. The sheer number and severity of these vulnerabilities underscore the importance of secure input validation and robust access control in PaaS solutions.
The batch of 25 vulnerabilities disclosed on August 10, 2026, for Dokploy highlights critical security weaknesses, primarily command injection flaws, affecting versions prior to 0.29.13. The timely patching in version 0.29.13 is crucial for users to secure their self-hosted PaaS environments.
Key Findings:
- A batch of 25 vulnerabilities, many critical (CVSSv3 9.9), were disclosed for Dokploy on August 10, 2026.
- The majority of flaws stem from command injection due to improper interpolation of user-controlled input into shell commands.
- Several vulnerabilities exploit authorization and access control weaknesses, allowing unauthorized command execution and data access.
- Path traversal and file system manipulation risks are present in multiple CVEs, impacting Git operations and Docker builds.
- All disclosed vulnerabilities were addressed in Dokploy version 0.29.13.
- Users are urged to update to version 0.29.13 immediately to mitigate these risks.
- Sensitive information such as GitHub secrets and database credentials could be exposed or misused.
- Flaws in WebSocket handlers and API endpoints allowed for unauthorized access and command execution.