What is the CVSS score of CVE-2026-72867?

CVE-2026-72867 has a CVSS 3.1 base score of 9.9 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. EPSS exploitation probability: 0.5%.

Which versions of Dokploy are affected by CVE-2026-72867?

Dokploy self-hosted PaaS versions 0.29.3 through 0.29.12 contain a critical authenticated command injection vulnerability (CVE-2026-72867, CVSS 9.9) that allows low-privileged users to execute…. A patch is available.

How to fix or mitigate CVE-2026-72867?

Within 24 hours, inventory all Dokploy deployments and identify systems running versions 0.29.3 through 0.29.12; document exposure based on internal user access levels and authentication mechanisms. Within 7 days, upgrade all affected instances to Dokploy 0.29.13 or later after backing up configurations and testing upgrades in non-production environments. Within 30 days, complete production rollout, review deployment audit logs for suspicious Git branch configurations created during the vulnerability window, and implement access controls restricting which roles can create or modify deployment Git branch field inputs.

Dokploy CVE-2026-72867

EUVD-2026-55725 CRITICAL

Improper Input Validation (CWE-20)

2026-08-10 GitHub_M

Information Disclosure Gitlab Dokploy Gitea

9.9

CVSS 3.1 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

9.9 CRITICAL

AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

vuln.today AI

9.9 CRITICAL

Network-reachable API with only a low-privileged account (PR:L) and no user interaction yields host command execution that escapes the app boundary (S:C) with full C/I/A impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch available

Aug 10, 2026 - 20:04 EUVD

Source Code Evidence Fetched

Aug 10, 2026 - 19:26 vuln.today

Analysis Generated

Aug 10, 2026 - 19:26 vuln.today

CVE Published

Aug 10, 2026 - 18:36 cve.org

CRITICAL 9.9

DescriptionCVE.org

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.

Articles & Coverage 1

News Critical Command Injection in Dokploy PaaS 0.29.3-0.29.12 - CVE-2026-72867 Aug 10, 2026

AnalysisAI

Authenticated command injection in Dokploy (self-hostable PaaS) versions 0.29.3 through 0.29.12 lets a low-privileged user achieve arbitrary host command execution by storing a malicious Git branch value and triggering a deployment. The branch fields (customGitBranch, branch, gitlabBranch, bitbucketBranch, giteaBranch) were left without server-side validation because the earlier fix for CVE-2026-45628 was incomplete, so attacker-controlled input flows unescaped into shell-based git clone commands. No public exploit has been identified at time of analysis, but the flaw carries a CVSS of 9.9 and is fixed in 0.29.13.

Technical ContextAI

Dokploy is a Vercel/Netlify-style Platform-as-a-Service that orchestrates Git-based deployments. The root cause is CWE-20 (Improper Input Validation): the compose schema in packages/server/src/db/schema/compose.ts persists branch fields directly, and the deploy path builds shell command strings by interpolating those fields into git clone --branch <branch> ... invocations across git.ts, github.ts, gitlab.ts, bitbucket.ts, and gitea.ts. Because the values reach a shell unescaped, shell metacharacters ($(...), backticks, ;, &&, |) are interpreted as commands rather than literal text. The upstream fix introduces a shellWord() escaping helper (wrapping branch, URL, output path, and hostname arguments) and adds a git-clone-command-injection test suite asserting that injection payloads collapse into a single inert shell token.

RemediationAI

Vendor-released patch: upgrade to Dokploy 0.29.13, which adds server-side shell escaping (the shellWord() helper) to all Git provider clone commands. This is the primary and recommended fix; consult advisory GHSA-cg8g-x23v-5fw8 and release v0.29.13. If immediate upgrade is not possible, reduce the attack surface by restricting who can create or hold low-privileged accounts and by limiting network access to the Dokploy management interface to trusted operators only (accepting that this blocks legitimate remote self-service). As an interim control, audit existing compose configurations for suspicious branch values containing shell metacharacters ($(), backticks, ;, &&, |) before any deploy is triggered, since malicious values may already be stored; note this is detective only and does not prevent a determined authenticated user from injecting new payloads.