Dokploy is an open-source, self-hosted deployment panel: you install it on your own VPS and it deploys applications and databases with Docker and Traefik; the project describes itself as an open-source alternative to Vercel, Netlify and Heroku. Between 08:14 and 08:29 UTC on November 12 it published 74 security advisories on GitHub at once: 30 critical, 27 high, 16 medium and 1 low. Most are fixed in 0.31.1, released at 08:12 UTC the same day, and a few in the earlier 0.31.0, 0.30.0 and 0.29.13; the latest version is 0.31.4, released on November 17.

What the flaws look like

  • The largest group is command injection that ends in root on the host. Changing a database password is one example (CVE-2026-129987, 9.9): the password validator missed the backtick, and the researcher showed on 0.31.0 that a crafted password made the panel run a command as root. Deleting a file mount (CVE-2026-129986), the publishDirectory parameter of Nixpacks builds (CVE-2026-129989) and the backup file name prefix (CVE-2026-129991) belong to the same group.
  • The second group is cross-organization access: about 145 endpoints did not check whether a resource belongs to the current organization, so a member of one organization could read and change another organization's projects, credentials and domains.
  • Others include members being able to see servers' SSH private keys (fixed in 0.29.13) and server-side request forgery (SSRF) through notification webhooks.

Who is most at risk

Of the 58 advisories that include a CVSS 3.1 vector, 56 require the attacker to have a panel account first; only 2 work without logging in, and neither is one of the direct-to-root kind. The researcher who disclosed the database password flaw on the oss-security mailing list put it plainly: it is not unauthenticated, and in a single-admin installation there is no boundary to cross. So the panels most at risk are shared ones: if you gave accounts to team members, contractors or customers, any one of them could use these flaws to take over the whole host and the secrets everyone else keeps on it. If yours is the only account, the risk is much lower, but the panel holds root and Docker on your servers, so update anyway.

What to do

  • Update to 0.31.1 or later, preferably straight to the latest version: on the server, run curl -sSL https://dokploy.com/install.sh | sh -s update, which pulls the latest image and updates the dokploy service.
  • Check the permissions of /etc/dokploy (CVE-2026-129315): the old install script ran chmod 777 /etc/dokploy, which lets any local user on the machine replace the root-owned scheduled-task scripts and Traefik configuration inside it, which then run as root the next time. The current install script uses 755, but the update command does not change an existing directory, so run sudo chmod 755 /etc/dokploy yourself. Machines that only you use are not affected by this one, because the attack needs another non-root local account on the machine.
  • The advisory for CVE-2026-129316 lists no fixed version; it affects 0.29.13 through 0.30.8, so moving to the 0.31 series takes you out of range.
  • While you are at it, review the panel's members and API keys and remove the ones you no longer use, then look for unfamiliar containers, bind mounts or scheduled tasks; if anything looks wrong, follow our intrusion check and hardening guide. It is best not to expose the panel's login page directly to the internet; allow only your own IP through the firewall, as covered in ufw firewall and SSH key login. Docker basics are in our Docker primer, and security settings for another popular panel are in our aaPanel installation and security guide.