CVE-2026-72878 in Dokploy is a shell injection via child_process.exec() in the backup pipeline that allows authenticated administrators to execute arbitrary commands on the host system. The CVSS 9.6 score is accurate, but it obscures the more important failure: Dokploy's security architecture inherits Docker's threat model without re-examining it for its new context.
Docker was designed as a developer tool on a single-user host—arbitrary command execution on that host is the expected behavior. Dokploy imports that same execution model while positioning itself as a PaaS that manages OTHER people's infrastructure. The distinction matters: an admin triggering a backup isn't just running a command on "a host"—they're running it on the same system that holds the Docker socket (often mounted directly), Traefik configuration with active Let's Encrypt credentials, application secrets and .env files for every managed project, database root passwords, and frequently SSH keys for deployment targets. Compromising the host means compromising the entire managed estate: every container's filesystem is reachable, new ACME certificates can be minted for arbitrary domains, and Traefik routing can be rewritten to MITM managed applications.
The "authenticated admin" prerequisite does not meaningfully constrain exploitation in self-hosted deployments where the admin IS the platform operator—this isn't privilege escalation, it's a direct execution path from a legitimate operator action to host-level code. The vulnerability collapses the multi-project isolation that users expect from a PaaS, even in single-operator setups.
The deeper pattern: infrastructure tooling has inherited shell-composition patterns through four generations (Docker CLI wrappers → CI/CD platforms → Kubernetes operators → PaaS abstractions), each inheriting the threat model of its predecessor without re-examining what's now at stake. The blast radius grew with each generation, but the execution model stayed the same. Backup pipelines are particularly vulnerable to this entropy—they're treated as plumbing, not part of the active attack surface, so shell interpolation persists in forgotten code paths long after better alternatives exist.
For defenders: audit other Dokploy subsystems for identical shell-composition patterns. The fix (0.29.13) patches the injection, but the architectural question remains—whether backup pipelines should execute on the host at all, or be isolated in a privileged but contained context. Given the remediation window for self-hosted platforms with no push mechanism, treat this as a high-priority patch but also as a signal to model your own threat model rather than inheriting one from the tools you deploy.