Description

Dokploy is a free, self-hostable Platform as a Service (PaaS). From 0.29.3 until 0.29.13, the incomplete fix for CVE-2026-45628 leaves packages/server/src/db/schema/compose.ts branch fields without server-side validation, allowing a direct compose.update request to store a malicious customGitBranch, branch, gitlabBranch, bitbucketBranch, or giteaBranch. A low-privileged authenticated user can trigger compose.deploy, which passes the stored branch to shell-based Git clone commands in packages/server/src/utils/providers/git.ts, github.ts, gitlab.ts, bitbucket.ts, and gitea.ts, resulting in arbitrary host command execution. This issue is fixed in version 0.29.13.

Executive Summary

Technical Details

Mitigations

References

Additional Metadata

{
  "score": "9.9",
  "pubDate": "2026-08-10T19:17:35.443Z",
  "pubdate": "2026-08-10T19:17:35.443Z",
  "executiveSummary": "An arbitrary host command execution vulnerability exists in Dokploy versions 0.29.3 through 0.29.13, stemming from an incomplete fix for CVE-2026-45628.\nThe vulnerability allows low-privileged authenticated users to supply malicious branch identifiers that are subsequently passed to shell-based Git clone commands, resulting in arbitrary host command execution.\nThe affected product is Dokploy, a self-hostable Platform as a Service (PaaS), specifically impacting database schema handling and Git provider utilities.\nSuccessful exploitation poses severe risk implications, potentially granting full system compromise and unauthorized control over the host infrastructure underlying the PaaS deployment.\nAttacker capabilities require low-privileged authentication to issue API requests that modify branch parameters and trigger deployment operations.",
  "technicalDetails": "The root cause of the vulnerability is the absence of server-side input validation on branch-related fields within packages/server/src/db/schema/compose.ts.\nAn incomplete fix for CVE-2026-45628 left customGitBranch, branch, gitlabBranch, bitbucketBranch, and giteaBranch fields vulnerable to manipulation during direct compose.update requests.\nThe exploitation method involves an authenticated low-privileged user leveraging the compose.update API endpoint to store arbitrary malicious strings within these branch fields.\nThe attack flow proceeds as the malicious user subsequently triggers the compose.deploy action.\nThe deployment utility passes the stored malicious branch values directly into shell-based Git clone commands located across multiple provider utility files: packages/server/src/utils/providers/git.ts, github.ts, gitlab.ts, bitbucket.ts, and gitea.ts.\nBecause the input lacks proper sanitization or parameterization before being executed in a shell context, crafted inputs achieve command injection.\nThe vulnerable components include the database schema definitions for compose configurations and the respective git provider integration utilities.\nThe affected software versions span from 0.29.3 to 0.29.13.\nAuthentication and low-level privileges are required to interact with the API endpoints for updating and deploying compose configurations.\nPost-exploitation impact includes arbitrary command execution on the host system running the Dokploy server, leading to potential complete takeover of the self-hosted PaaS environment."
}