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

Dokploy versions prior to 0.29.13 contain a command injection vulnerability allowing authenticated team members with project write access to execute arbitrary commands on the server infrastructure,…. A patch is available.

How to fix or mitigate CVE-2026-72870?

Within 24 hours, audit and restrict project write access to only essential personnel, enable detailed command execution logging on all Dokploy servers, and compile a list of current version deployments. Within 7 days, implement input validation controls on the dockerImage parameter to block shell metacharacters as a temporary defensive measure, escalate this CVE to Dokploy maintainers requesting patch timeline, and review command execution logs for suspicious activity. Within 30 days, prepare and stage an upgrade to version 0.29.13 or later when released, evaluate network segmentation to limit Dokploy server access, and consider deploying a Web Application Firewall with rules to sanitize dockerImage inputs.

Dokploy CVE-2026-72870

Q: What is the CVSS score of CVE-2026-72870?

CVE-2026-72870 has a CVSS 4.0 base score of 8.7 (High). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.3%.

EUVD-2026-55730 HIGH

OS Command Injection (CWE-78)

2026-08-10 GitHub_M

Docker Command Injection Dokploy

8.7

CVSS 4.0 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

8.7 HIGH

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

8.8 HIGH

Network-reachable API requires only project-level authentication (PR:L); full RCE as server process within the same security scope (S:U); all three CIA impacts are high.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/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:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M).

CVSS VectorVendor: GitHub_M

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Patch available

Aug 10, 2026 - 20:04 EUVD

Source Code Evidence Fetched

Aug 10, 2026 - 19:25 vuln.today

Analysis Generated

Aug 10, 2026 - 19:25 vuln.today

CVE Published

Aug 10, 2026 - 18:45 cve.org

HIGH 8.7

DescriptionCVE.org

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, the buildRemoteDocker() function in packages/server/src/utils/providers/docker.ts interpolates the application-controlled dockerImage value directly into a docker pull shell command. An authenticated user with project access can set a crafted dockerImage through application.update and trigger application.deploy, causing execAsync() to execute arbitrary operating-system commands as the Dokploy server process. This issue is fixed in version 0.29.13.

AnalysisAI

OS command injection in Dokploy prior to version 0.29.13 allows any authenticated user with project write access to execute arbitrary commands as the Dokploy server process. The buildRemoteDocker() function in packages/server/src/utils/providers/docker.ts interpolates the user-controlled dockerImage field directly into a shell command passed to execAsync() without sanitization. The same unsanitized interpolation pattern was present across three separate build pipeline files, indicating a systemic rather than isolated flaw. No public exploit has been identified at time of analysis, and the vulnerability is not listed in CISA KEV.

Technical ContextAI

Dokploy is a self-hosted Node.js PaaS that orchestrates Docker-based application deployments. The vulnerable sink is execAsync(), which passes a shell-interpolated command string to /bin/sh. The root cause (CWE-78, OS Command Injection) arises from template literal construction such as 'docker pull ${dockerImage}' where dockerImage is application-supplied data set via the application.update API. The same anti-pattern existed in packages/server/src/utils/builders/docker-file.ts (dockerContextPath field used in cd and echo commands) and packages/server/src/utils/builders/nixpacks.ts (publishDirectory field used in docker cp). The fix in PR #4860 and commit cba0b253c7de4157dd932de7f16a2ad247c7cee9 applies the shell-quote library uniformly across all three files, wrapping every user-controlled value with quote([value]) before interpolation. CPE cpe:2.3:a:dokploy:dokploy:*:*:*:*:*:*:*:* covers all Dokploy releases prior to 0.29.13.

RemediationAI

Upgrade Dokploy to version 0.29.13 or later, which is confirmed by the GitHub release tag at https://github.com/Dokploy/dokploy/releases/tag/v0.29.13 and the upstream fix commit cba0b253c7de4157dd932de7f16a2ad247c7cee9. The fix applies shell-quote escaping to all user-controlled values across the docker.ts, docker-file.ts, and nixpacks.ts build pipeline files. If immediate upgrade is not feasible, restrict project write access to fully trusted accounts only, removing any shared, externally-provisioned, or contractor accounts from Dokploy project membership, as any such account can serve as an exploitation vector. As a depth-in-defense measure, run the Dokploy server process under a least-privilege OS user account to limit the blast radius of command injection - note this does not eliminate the vulnerability and may still permit reads of sensitive files or lateral movement within the server environment. No workarounds exist that neutralize the injection without applying code changes.