Dokploy: authenticated members inject shell commands into deploy and backup paths and get host root

Impact

Dokploy builds shell strings by interpolating user-controlled fields - registry credentials, Swarm cluster parameters, database image names, compose file paths, git branch names, rclone destination fields and backup database names - and runs them through /bin/sh, locally or over SSH to a managed remote server. Any authenticated organization member who can reach one of those mutations executes arbitrary commands as root inside the Dokploy container, which mounts the host Docker socket, so the result is root on the machine and on every remote server the instance manages. On a node that also runs accelerator workloads this collapses the boundary between a project member and the host: the attacker can read other tenants' containers, images and secrets, and can pin or reconfigure anything scheduled there. The vendor split this across six ids (CVE-2026-72736, -72862, -72865, -72867, -72868, -72869) covering different endpoints, but they are one flaw class in one component with one fixed release; CVE-2026-72867 is noted as an incomplete fix for the earlier CVE-2026-45628.

Who can reach it

Network access to the Dokploy web/API endpoint with any authenticated organization member account - low-privileged roles holding only create or deploy permissions on a single project are enough. No host access, no admin role, and no user interaction by another party.

What to do

Upgrade to Dokploy 0.29.13 and restart the Dokploy stack; the advisories publish no configuration-only mitigation. Until the upgrade lands, treat every member account on the instance as equivalent to host root and cut membership to operators you would already trust with the Docker socket. This is an application-container restart, not a node reboot, but it interrupts the control plane that deploys your workloads, so schedule it outside a deploy window.

Also covers 5 CVEs

The vendor assigned a separate id to each affected code path. They share this advisory, this score and this fix, so they are one entry here.

References

Related entries

• Dokploy: WebSocket terminals authenticate but never authorize, giving any member a root shell in any containerCVE-2026-72863 · Dokploy WebSocket handlers (container terminal and log streaming)Critical
• KubeVirt: Improper symlink validation in virt-handler lets a user with edit rights in one namespace escape to the hostCVE-2026-7374 · KubeVirtCritical
• Helm: Improper certificate validation allows unauthorized clients to connect to TillerCVE-2019-1010275 · HelmCritical
• Docker / moby: Code injection into `docker cp` via nsswitch loading a library from the container chrootCVE-2019-14271 · Docker / mobyCritical
• Helm: Malicious chart includes sensitive host content such as /etc/passwd, or triggers DoS, when loadedCVE-2019-18658 · HelmCritical
• Envoy: HTTP/2 request writes to the heap outside request buffers when the upstream is HTTP/1CVE-2019-18801 · EnvoyCritical