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

Dokploy self-hosted PaaS versions before 0.29.8 contain a critical command injection vulnerability that allows authenticated users with project access to execute arbitrary commands with host-level…. A patch is available.

How to fix or mitigate CVE-2026-72879?

Within 24 hours, identify all Dokploy instances in your environment and verify their current versions. Within 7 days, develop and test an upgrade plan to deploy version 0.29.8 or later in a staging environment to validate compatibility with your applications and infrastructure. Within 30 days, complete the upgrade of all production Dokploy instances to version 0.29.8 or later.

Dokploy CVE-2026-72879

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

CVE-2026-72879 has a CVSS 4.0 base score of 9.4 (Critical). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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-55745 CRITICAL

OS Command Injection (CWE-78)

2026-08-10 GitHub_M

Docker Command Injection Dokploy

9.4

CVSS 4.0 · Vendor: GitHub_M

Severity by source

Vendor (GitHub_M) PRIMARY

9.4 CRITICAL

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/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

9.9 CRITICAL

Authenticated project user (PR:L) injects commands over the network (AV:N/AC:L); code executes on the host and reaches other containers, so scope changes (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

Lifecycle Timeline

Patch available

Aug 10, 2026 - 20:04 EUVD

Source Code Evidence Fetched

Aug 10, 2026 - 19:51 vuln.today

Analysis Generated

Aug 10, 2026 - 19:51 vuln.today

CVE Published

Aug 10, 2026 - 19:14 cve.org

CRITICAL 9.4

DescriptionCVE.org

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.8, the getRegistryCommands() function in packages/server/src/utils/cluster/upload.ts interpolates registry.password and registry.registryUrl directly into a shell command without escaping. An authenticated user with project access can configure malicious registry credentials and trigger a swarm deployment to execute arbitrary OS commands on the Dokploy server, read or modify host files, and access other containers through Docker. This issue is fixed in version 0.29.8.

AnalysisAI

OS command injection in Dokploy self-hosted PaaS before 0.29.8 allows an authenticated user with project access to run arbitrary commands on the Dokploy host. The getRegistryCommands() function in packages/server/src/utils/cluster/upload.ts builds a docker login shell string by interpolating the attacker-controlled registry password and URL without escaping, so malicious credentials are executed when a swarm deployment runs. No public exploit identified at time of analysis, but the root cause and fix are fully disclosed in the vendor advisory (GHSA-prwq-2mcm-mvhr), PR #4579, and the v0.29.8 release.

Technical ContextAI

Dokploy is an open-source, self-hostable Platform-as-a-Service (a Heroku/Vercel alternative) that orchestrates application deployments via Docker Swarm. The flaw is a classic CWE-78 (Improper Neutralization of Special Elements used in an OS Command). Registry credentials are consumed by getRegistryCommands(), which originally produced the shell line echo "${registry.password}" | docker login ${registry.registryUrl} -u '${registry.username}' --password-stdin. Because registry.password and registry.registryUrl are interpolated directly into a string later handed to a shell, characters such as ", $(...), backticks, or ; break out of the intended docker login command. The fix (PR #4579) centralizes login-string construction in a new safeDockerLoginCommand() helper - applied in upload.ts, providers/docker.ts, and services/registry.ts - and adds sanitizeRegistryError() so credentials are not leaked back in error messages. CPE cpe:2.3:a:dokploy:dokploy:*:*:*:*:*:*:*:* identifies the affected application.

RemediationAI

Vendor-released patch: 0.29.8 - upgrade all Dokploy server instances to v0.29.8 or later, which replaces raw string interpolation with the safeDockerLoginCommand() helper (see PR https://github.com/Dokploy/dokploy/pull/4579 and commit 1f4f94042f1d874349c42d8ae7fee51346cd086e). Until patched, restrict registry-configuration and deployment permissions to fully trusted operators only, and audit existing registry entries for suspicious password or URL values containing shell metacharacters (quotes, $(, backticks, semicolons); note this compensating control does not close the hole and only shrinks the trusted attacker set. Because the injected commands run with the Dokploy server's Docker access, also review the advisory at https://github.com/Dokploy/dokploy/security/advisories/GHSA-prwq-2mcm-mvhr and consider isolating the Dokploy host from other sensitive workloads until the upgrade is completed.