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

CVE-2026-72872 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.4%.

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

Dokploy self-hosted PaaS (versions before 0.29.13) suffers a critical command injection vulnerability allowing low-privileged team members with deployment permissions to execute arbitrary commands on…. A patch is available.

How to fix or mitigate CVE-2026-72872?

Within 24 hours, identify all Dokploy instances in your infrastructure and confirm which versions are deployed; immediately restrict service-deployment permissions to trusted personnel only and enable comprehensive logging of deployment activities. Within 7 days, upgrade all Dokploy deployments to version 0.29.13 or later, beginning with non-production environments to verify compatibility. Within 30 days, audit all deployment logs for suspicious command execution, validate that access controls remain properly restricted, and document patch deployment for compliance verification.

Dokploy CVE-2026-72872

EUVD-2026-55733 CRITICAL

OS Command Injection (CWE-78)

2026-08-10 GitHub_M

Command Injection Dokploy

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 web action needing only low-privileged deployment permission (PR:L, AV:N, AC:L); injected commands escape the app to run on the host OS, giving a scope change (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:23 vuln.today

Analysis Generated

Aug 10, 2026 - 19:23 vuln.today

CVE Published

Aug 10, 2026 - 18:50 cve.org

CRITICAL 9.9

DescriptionCVE.org

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, application.saveBitbucketProvider stores bitbucketOwner and bitbucketRepository without validation and cloneBitbucketRepository in packages/server/src/utils/providers/bitbucket.ts interpolates those values into git clone commands executed through execAsync or execAsyncRemote, allowing a member with service deployment permission to execute arbitrary operating system commands on the Dokploy host or target server. This issue is fixed in version 0.29.13.

AnalysisAI

OS command injection in Dokploy (self-hosted PaaS) before 0.29.13 lets a low-privileged team member with service-deployment permission run arbitrary commands on the Dokploy host or a connected target server. The saveBitbucketProvider endpoint persists attacker-controlled bitbucketOwner and bitbucketRepository values without validation, and cloneBitbucketRepository later interpolates them straight into git clone commands run via execAsync/execAsyncRemote. There is no public exploit identified at time of analysis, but the fix (0.29.13) ships regression tests demonstrating the injection payloads, so the mechanism is well documented.

Technical ContextAI

Dokploy is an open-source, self-hostable Platform-as-a-Service (a Heroku/Vercel alternative) that orchestrates container deployments and integrates with Git providers including Bitbucket. The flaw is a classic CWE-78 OS Command Injection: in packages/server/src/utils/providers/bitbucket.ts the clone routine builds a shell string of the form git clone --branch <branch> ... <cloneUrl> <outputPath> and executes it through a shell (execAsync locally or execAsyncRemote over SSH). Because Bitbucket owner/repository/branch values are stored unvalidated and concatenated rather than passed as separated arguments, shell metacharacters ($( ), backticks, ;, &&, |) in those fields are interpreted by the shell. The CPE cpe:2.3:a:dokploy:dokploy:*:*:*:*:*:*:*:* confirms the affected product is the Dokploy application itself across all versions prior to the fix. The upstream patch introduces a shellWord() escaping helper and applies it across the Bitbucket, generic Git, and Gitea providers.

RemediationAI

Vendor-released patch: upgrade to Dokploy 0.29.13 or later (release https://github.com/Dokploy/dokploy/releases/tag/v0.29.13), which introduces a shellWord() shell-escaping helper applied to the Bitbucket, Git, and Gitea clone routines; see advisory GHSA-grrj-6xrh-j6vp and PR #4855. If you cannot patch immediately, reduce exposure by restricting who holds service-deployment permission to a minimal set of fully trusted operators, since that role is the prerequisite for exploitation; avoid delegating deployment rights in multi-tenant setups. As an additional compensating control, audit and constrain existing Bitbucket provider configurations (bitbucketOwner/bitbucketRepository/branch) for shell metacharacters, and where feasible run the Dokploy host with reduced blast radius (least-privilege service account, network segmentation for any execAsyncRemote target servers) - noting this does not close the injection, only limits post-exploitation reach. These are stopgaps only; upgrading is the sole complete fix.