Dokploy’s WebSocket handlers authenticates a user but does not enforce the role or permission model used by other tRPC procedures. An authenticated member can therefore open an interactive shell into any container, including the container that mounts the Docker socket, and from there gain root permissions on the host. The flaw is a classic privilege‑escalation vulnerability that allows a low‑privilege user to escape the application sandbox and subvert all tenant boundaries.

This vulnerability affects all Dokploy editions older than release 0.29.13. Any instance where the Dokploy container has access to the Docker socket and where low‑privilege members are registered is susceptible. The fix begins at version 0.29.13 and later versions include proper authorization checks in their WebSocket endpoints.

The CVSS score of 9.9 classifies this as Critical, and the EPSS score is not available, indicating no publicly reported exploitation patterns yet. It is not listed in the CISA KEV catalog. The likely attack vector is remote, via the WebSocket endpoint exposed over the network; an attacker only needs a valid authenticated account with low privileges. Once the WebSocket is accessed, the attacker immediately controls a container that can manipulate the Docker socket, achieving full host control. The combination of high severity, potential for rapid host compromise, and the simple authentication prerequisite makes this a high‑risk scenario for any operational deployment.