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

Dokploy versions prior to v0.29.13 expose organizations to remote command execution on production infrastructure through an authenticated user vulnerability in service deployment controls.. A patch is available.

How to fix or mitigate CVE-2026-72884?

Within 24 hours: Audit all Dokploy deployments to identify current versions and enumerate users with Compose service edit permissions. Within 7 days: Upgrade all affected instances to v0.29.13 or later and apply the vendor patch, then restrict Compose service edit permissions to only essential personnel with documented business justification. Within 30 days: Review audit logs for any suspicious compose service modifications, conduct a full access control review of Compose service permissions, and implement enhanced monitoring for compose command execution activity.

Dokploy CVE-2026-72884

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

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

EUVD-2026-55794 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-exploitable by any authenticated Compose editor (AV:N, PR:L); low complexity; full C/I/A impact on Dokploy host; scope unchanged as the host is the primary impacted system.

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 - 21:05 EUVD

Source Code Evidence Fetched

Aug 10, 2026 - 20:05 vuln.today

Analysis Generated

Aug 10, 2026 - 20:05 vuln.today

CVE Published

Aug 10, 2026 - 19:30 cve.org

HIGH 8.7

DescriptionCVE.org

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, sanitizeCommand in packages/server/src/utils/builders/compose.ts only trims whitespace and strips surrounding quotes from compose.command before exportEnvCommand and docker command interpolation, allowing an authenticated user who can update a Compose service to inject shell metacharacters and execute arbitrary commands on the Dokploy host. This issue is fixed in version 0.29.13.

AnalysisAI

Shell command injection in Dokploy exposes the underlying host OS to arbitrary command execution by any authenticated user with Compose service edit permissions. The flaw is in the sanitizeCommand function within packages/server/src/utils/builders/compose.ts, which stripped only whitespace and surrounding quotes before interpolating user-supplied compose.command values into live shell invocations such as docker ${command} - leaving semicolons, pipe operators, backticks, and subshell substitutions entirely intact. Working exploit payloads (semicolons, $(subshell), pipes, backtick substitution) are publicly available in the fix PR test suite at https://github.com/Dokploy/dokploy/pull/4863; no CISA KEV listing exists at time of analysis, and the vendor-confirmed patch is available in v0.29.13.

Technical ContextAI

Dokploy is a self-hosted, open-source Platform as a Service built atop Docker Compose and Docker Swarm stack management. The vulnerable code path originates in packages/server/src/utils/builders/compose.ts where the sanitizeCommand function accepted a user-controlled compose.command string, applied only .trim() and quote-character stripping, then inserted the result unsanitized into shell command strings. The same pattern affected appName and composePath interpolation in both the compose builder and packages/server/src/services/compose.ts, where values like compose.appName were embedded directly into env -i PATH=$PATH docker compose -p ${compose.appName} -f ${path} up -d without escaping. CWE-78 (Improper Neutralization of Special Elements Used in an OS Command) precisely describes the root cause: user-controlled data entered a shell execution context without proper neutralization. The fix in PR #4863 introduced the shell-quote library to properly shell-escape appName, path, and envFilePath arguments throughout the codebase, and added a strict regex blocklist (/[;&|`$(){}<> \\]/) on compose command fields that throws an error rather than attempting to sanitize dangerous input. CPE cpe:2.3:a:dokploy:dokploy:*:*:*:*:*:*:*:* covers all affected pre-fix versions.

RemediationAI

Upgrade to Dokploy v0.29.13 immediately - this is the vendor-confirmed patched release (https://github.com/Dokploy/dokploy/releases/tag/v0.29.13), which replaces unsafe raw string interpolation with shell-quote escaping for appName, composePath, and envFilePath arguments throughout both the compose builder and compose service, and adds regex validation that rejects shell control characters in user-supplied compose command fields. The fix is backwards-compatible and has no documented side effects on legitimate compose workflows, as confirmed by the test cases in PR #4863 that verify benign commands like compose -f docker-compose.yml -p app up -d --build pass through correctly. If an immediate upgrade is not feasible, restrict Compose service edit permissions exclusively to fully trusted administrative accounts - this narrows the exploitable attack surface but does not eliminate the vulnerability, as any remaining Compose editor retains exploitation capability. There is no documented configuration toggle or network-layer control that removes the vulnerable code path while preserving Compose deployment functionality.