Dokploy: authenticated member gets host root RCE via database password injection (CVE-2026-129987)
Severity: critical · Patch status: patched · Since 2026-11-12 · CVE-2026-129987
Dokploy before 0.31.1 lets an authenticated organization member who holds service:create on a database service run commands as the Dokploy server process, which is usually root in a container that holds the host's Docker socket. The changePassword procedures for MySQL, PostgreSQL, MariaDB, MongoDB and Redis put the new password into a shell string inside double quotes, and the password validator still accepts backticks, so a backtick subshell in the password runs on the host. The reporter's writeup also says the database username reached the shell unquoted. The 0.31.1 fix does not change the validator; it passes every argument through a quoting helper, so backtick passwords are now stored literally. The vendor rated the issue CVSS 9.9 and shipped the fix in 0.31.1 on 2026-11-12. The GitHub advisory contains manual reproduction steps and a short script, so a public proof of concept exists. No in-the-wild exploitation report or CISA KEV entry was found. Upgrade to 0.31.1 or later; until then, withdraw service:create from members who do not need it.
What to do
- Upgrade Dokploy to 0.31.1 or later immediately; if you cannot, restrict access and remove service create/update permissions from untrusted members.
- Audit Dokploy and database logs for password or username changes containing backticks, semicolons, command substitution, or redirects, and investigate the host/container for compromise.
- Rotate database credentials and other secrets accessible to Dokploy, and review Docker socket exposure and tenant isolation.
- Limit service:create permission to trusted administrators and monitor for unusual child processes spawned by the Dokploy process.
Fixed versions
Sources
All live incidents on Threat Watch