The vulnerability CVE-2026-129433 turns a plain member account in Dokploy into root access on the server. Dokploy is an open-source, self-hosted platform for deploying applications and databases that describes itself on GitHub as an open-source alternative to Vercel, Netlify and Heroku. Through an unvalidated field in its backup feature, authenticated users with member rights can inject arbitrary shell commands. The flaw is fixed in version 0.31.1, and the project advisory includes a public proof of concept.
What CVE-2026-129433 is about
According to the GitHub security advisory GHSA-j329-jw7j-rxjm from 12 November 2026, the bug sits in the function getComposeContainerCommand() in packages/server/src/utils/backups/utils.ts. It assembles a docker ps command meant to find the matching container of a Docker Compose service. The service name serviceName was placed unchanged into a filter inside double quotes. The command runs through execAsync with /bin/bash as the shell.
The value comes from the tRPC procedures backup.create and backup.update. The Zod schema validated serviceName only as an arbitrary string, while other shell-adjacent fields in the same schema had strict validators. An attacker can therefore store a service name containing quotes, a semicolon and their own commands. Once the scheduled backup job runs, Bash executes those commands. The default schedule in the advisory’s examples is */1 * * * *, every minute, so the injected instruction runs within about 60 seconds.
From member account to root on the host
What matters is the privilege the code runs with and what it can reach. The backup command executes as root inside the Dokploy container. Because Dokploy mounts the Docker socket /var/run/docker.sock on standard installations, that leads to full control of the host. The advisory rates the flaw CVSS 9.9 out of 10. The independent database VulnCheck lists it under the newer CVSS 4.0 metric at 9.4 and rates it “critical”.
The low barrier to entry is especially concerning. The attack only needs a member account with access to a single project and the right to create backups. No admin or owner privileges are required. It also needs only the ID of an existing backup destination, not its credentials. The flaw therefore falls into the “member → root” category: privilege escalation from a limited team member to full server takeover.
The proof of concept
The advisory documents the flow step by step: sign in as a member, create a Compose app, then issue a backup.create call whose serviceName field carries a service name with an appended command, for example running id followed by sending the data to an external server. The response, according to the advisory, is a normal HTTP 200. Within a minute at most, the attacker’s server receives the command output, which begins with uid=0(root). The advisory also includes a self-contained Python script that automates the flow. The existence of a public proof of concept raises the urgency of updating significantly.
CVE-2026-129433 is part of a larger cleanup
The flaw is not an isolated case. The release notes for version 0.31.1 list dozens of security fixes at once. They include further command-injection flaws in backups, schedules, database password changes and build fields, plus cross-organisation access problems where users could reach other organisations’ SSH keys, registry passwords or services, and several SSRF bugs. Many of these findings came from the maintenance team itself, according to the release. As a fix, the advisory recommends restricting serviceName with a strict Zod regex or using the shell-quote library already in the project to quote values safely.
What operators should do now
The most important step is updating to Dokploy 0.31.1 or later. At the time of writing, 0.31.2 is already available. Operators should also review existing backup definitions and remove any with suspicious characters such as quotes, semicolons, backticks or $() in the service name, because injected commands keep running on every job until the update is applied. Anyone who has granted member accounts to external people should audit the related activity. As a general rule, it remains sensible not to mount the Docker socket into containers unless necessary, even though deployment platforms like Dokploy commonly do so by design.
The flaw fits a series of command-injection and privilege-escalation bugs in developer and deployment tooling. We recently reported on an actively exploited root flaw in Check Point systems and on the security incident at the developer platform Railway. The pattern is similar each time: user input reaches a shell or a privileged context without validation.
Bottom line
CVE-2026-129433 is a critical OS command injection in Dokploy before version 0.31.1. A member account is enough to run commands as root through an unvalidated backup field and to take over the host via the mounted Docker socket. With CVSS 9.4 under version 4.0, a public proof of concept and an available fix, the update should not wait. If you run Dokploy yourself, update now and review your existing backup configurations.



