A critical OS command injection vulnerability, tracked as CVE-2026-129433, affects Dokploy, the self-hosted deployment platform. In versions before 0.31.1, an authenticated member of a Dokploy organization can store a malicious value in a backup’s service name. That value later runs as shell commands with root privileges when the scheduled backup executes.
Because Dokploy has the Docker socket mounted, an attacker who gets command execution this way can take over the underlying host. The flaw has a CVSS score of 9.9 (Critical). It is not listed in CISA’s Known Exploited Vulnerabilities catalog, and the supplied records contain no reports of exploitation.
What’s affected
According to the NVD record, all Dokploy versions before 0.31.1 are affected. Version 0.31.1 is listed as unaffected.
The vulnerable code is in the getComposeContainerCommand() function, which builds the command used to back up Docker Compose services. The serviceName parameter is not handled safely, so shell metacharacters in it end up in the executed command (CWE-78). An attacker can set a malicious serviceName through the backup.create or backup.update tRPC procedures. The injected commands run when the scheduled backup next fires, not when the value is saved.
How serious is it
NVD scores the flaw 9.9 out of 10 with the vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. In plain terms:
- Network attack vector, low complexity: the attack can be carried out remotely through Dokploy’s API, with no special conditions.
- Low privileges required: the attacker needs an account, but only as an ordinary organization member, not an administrator.
- No user interaction: no one else has to click or approve anything. The scheduled backup triggers the payload.
- Scope changed: the impact reaches beyond Dokploy itself. Commands run as root, and the mounted Docker socket gives control of the host and its other containers.
- High confidentiality, integrity and availability impact: a successful attacker could read, change or destroy data and disrupt every service on the host.
Organizations that give Dokploy access to many people are most exposed. That includes contractors, multiple teams, and customers in shared or multi-tenant setups. Any one of those accounts could be used to compromise the whole server.
Is it being exploited?
As of the record date (15 November 2026), CVE-2026-129433 is not in CISA’s Known Exploited Vulnerabilities catalog. The supplied records contain no reports of exploitation in the wild.
The NVD entry was published on 14 November 2026 and has the status “Deferred”. The project’s code, fix commit and pull request are all public, so administrators should not wait for exploitation reports before patching.
What to do
- Upgrade to Dokploy 0.31.1 or later. The NVD record lists 0.31.1 as the first unaffected version. See the release notes and the GitHub security advisory linked below.
- Review organization membership. Remove accounts that no longer need access, and limit membership to trusted users until you have upgraded.
- Audit existing backup configurations. Check compose backup entries for service names that contain unexpected characters. A malicious value saved before the upgrade could already have run on a schedule.
- Check for signs of compromise if untrusted users had access to a vulnerable version. Look for unexpected containers, processes, cron jobs or SSH keys on the host. Successful exploitation means root-level control.
- Restrict exposure. Keep the Dokploy dashboard and API off the public internet where possible, or put them behind a VPN or access proxy.

