Dokploy: compose service names are interpolated into shell commands, giving command execution on the Docker host

Impact

Dokploy builds deployment shell commands by string-interpolating compose service names and configuration, so a project member who can define or deploy a compose stack gets arbitrary command execution as the Dokploy process on the Docker host. On a shared build or deployment host that means escaping the tenant's own project boundary and reaching every other stack, its environment variables and registry credentials on the same machine. Where Dokploy fronts GPU nodes, the same path reaches the container runtime that schedules accelerator workloads.

Who can reach it

Any authenticated Dokploy user with permission to create or deploy a compose application; no host access and no administrative role is required beyond that.

What to do

Upgrade to Dokploy 0.29.13 and restart the Dokploy service; the fix is in the deployment path only, so no host reboot or node drain is needed. Running deployments are unaffected by the restart, but treat any host that ran an untrusted compose definition as suspect and rotate credentials reachable from it.

References

Related entries

• Kubernetes (kube-apiserver): Unvalidated redirect on proxied upgrade requests lets a compromised node escalate to otherCVE-2020-8559 · Kubernetes (kube-apiserver)Medium
• Harbor: Robot accounts in other projects can be updatedCVE-2022-31667 · HarborMedium
• Harbor: Incorrect permission validation lets authenticated users modify Harbor configurationCVE-2024-22278 · HarborMedium
• Helm: Relative path in a chart name writes the chart outside the intended directoryCVE-2024-25620 · HelmMedium
• KubeVirt: SSRF in the virt-api port-forward handler via attacker-influenced VMI status IPCVE-2026-13318 · KubeVirtMedium
• Traefik: A tenant with HTTPRoute creation rights exposes the REST provider handler, bypassing provider isolationCVE-2026-44774 · TraefikMedium