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

CVE-2026-72736 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-72736?

Dokploy self-hosted PaaS (versions before 0.29.13) contains a critical vulnerability allowing authenticated dashboard users to execute arbitrary commands on managed remote infrastructure, risking…. A patch is available.

How to fix or mitigate CVE-2026-72736?

Within 24 hours, restrict dashboard access to essential administrators and enable comprehensive audit logging of all dashboard activities. Within 7 days, review dashboard access logs for exploitation attempts and implement network segmentation to isolate dashboard servers from production remote nodes. Within 30 days, monitor vendor updates and establish procedures to apply patches immediately upon release; also evaluate disabling remote node management features entirely if patches remain unavailable.

Dokploy CVE-2026-72736

EUVD-2026-55684 CRITICAL

Command Injection (CWE-77)

2026-08-10 GitHub_M

Docker 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

Authenticated dashboard user (PR:L) sends network requests with low complexity; injected command escapes the app to fully compromise the remote SSH host (S:C, C/I/A:H).

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 - 19:03 EUVD

Source Code Evidence Fetched

Aug 10, 2026 - 18:32 vuln.today

Analysis Generated

Aug 10, 2026 - 18:32 vuln.today

CVE Published

Aug 10, 2026 - 17:40 cve.org

CRITICAL 9.9

DescriptionCVE.org

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, Dokploy passes user-controlled values directly into shell commands via unquoted template literal interpolation in the registry credential testing and Docker Swarm cluster management endbpoints. Both endpoints have a safe local code path (using execFileAsync or the Docker API) but a vulnerable remote path (using execAsyncRemote which runs the shell string via SSH). This vulnerability is fixed in 0.29.13.

Articles & Coverage 1

News Critical RCE in Dokploy Self-Hosted PaaS before 0.29.13 - CVE-2026-72736 Aug 10, 2026

AnalysisAI

Remote command injection in Dokploy self-hosted PaaS before 0.29.13 allows an authenticated dashboard user to execute arbitrary shell commands on managed remote nodes. The registry credential-testing and Docker Swarm cluster-management endpoints interpolate user-controlled values (nodeId, imagePrefix/username driving the registry tag) into unquoted shell strings that run over SSH via execAsyncRemote. Rated CVSS 9.9 with scope change; no public standalone exploit is identified, though the public fix commit df2779e and advisory GHSA-4mfc-grxw-6858 disclose the exact vulnerable code paths and injection payloads.

Technical ContextAI

Dokploy is an open-source, self-hostable Platform-as-a-Service (a Heroku/Vercel alternative) that orchestrates Docker and Docker Swarm across local and remote nodes. The root cause is CWE-77 (Command Injection): several code paths build shell command strings with JavaScript template-literal interpolation, e.g. docker node update --availability drain ${input.nodeId}, docker node rm ${input.nodeId} --force, and registry docker tag/docker push commands where the registry tag is assembled from registryUrl/username/imagePrefix. Per the source evidence, username and imagePrefix have no schema/regex validation. Each operation has two execution paths: a safe local path using execFileAsync or the Docker API (argument-array based, not shell-parsed), and a vulnerable remote path where execAsyncRemote ships the assembled string to a remote host and executes it through /bin/sh over SSH - so metacharacters like $(...), backticks, ;, and | are interpreted by the shell. The fix wraps every interpolated value with shell-quote's quote() across cluster.ts, upload.ts, and gpu-setup.ts.

RemediationAI

Vendor-released patch: upgrade to Dokploy 0.29.13 or later, which wraps all user-controlled interpolations with shell-quote's quote() in cluster.ts, upload.ts, and gpu-setup.ts (fix commit df2779e; release https://github.com/Dokploy/dokploy/releases/tag/v0.29.13; advisory https://github.com/Dokploy/dokploy/security/advisories/GHSA-4mfc-grxw-6858). If immediate patching is not possible, reduce exposure by restricting Dokploy dashboard accounts to trusted administrators only and removing cluster-management and registry-configuration privileges from lower-trust users (trade-off: those users lose self-service node/registry management), and prefer local-only management (execFileAsync/Docker API path) over remote SSH-managed nodes where feasible, since the local path is not vulnerable (trade-off: loses multi-node remote orchestration). Network-restrict access to the Dokploy management UI so only administrators can reach the affected endpoints (trade-off: remote operators must use a VPN/bastion). These are stopgaps; upgrading to 0.29.13 is the definitive fix.