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

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

Dokploy before version 0.29.13 contains a command injection vulnerability in its backup restoration feature that allows authenticated users with backup:restore permission to execute arbitrary…. A patch is available.

How to fix or mitigate CVE-2026-72869?

Within 24 hours: Inventory all Dokploy deployments, identify current versions, and audit which users hold the backup:restore permission-restrict immediately to only essential administrators. Enable comprehensive audit logging for all backup operations and configure alerts for unusual activity. Within 7 days: Monitor vendor channels for Dokploy version 0.29.13 or later release; establish a staging environment to validate the upgrade; implement approval workflows requiring multi-person authorization for any backup restore request. Within 30 days: Deploy Dokploy version 0.29.13 or later to all production and non-production environments; confirm backup and restore functionality operate correctly; enforce permanent controls limiting backup:restore access and document change procedures.

Dokploy CVE-2026-72869

EUVD-2026-55728 CRITICAL

Command Injection (CWE-77)

2026-08-10 GitHub_M

Docker PostgreSQL Command Injection Node.js 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 tRPC endpoint (AV:N/AC:L) requires a low-privilege backup:restore account (PR:L), no interaction (UI:N), and injected code escapes the container to the Docker-privileged host (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:25 vuln.today

Analysis Generated

Aug 10, 2026 - 19:25 vuln.today

CVE Published

Aug 10, 2026 - 18:40 cve.org

CRITICAL 9.9

DescriptionCVE.org

Dokploy is a free, self-hostable Platform as a Service (PaaS). Prior to 0.29.13, the backup.restoreBackupWithLogs tRPC subscription passes the databaseName parameter to restore builders in packages/server/src/utils/restore/utils.ts, where PostgreSQL, MariaDB, MySQL, and MongoDB commands embed the value in nested shell text executed by Node.js exec. An authenticated user with backup:restore permission can supply a crafted databaseName that the host /bin/sh expands before docker exec, resulting in arbitrary commands running in the Docker-privileged host context. This issue is fixed in version 0.29.13.

Articles & Coverage 2

News 3 Critical PostgreSQL Vulnerabilities Patched - Immediate Update Required Aug 11, 2026 News Critical OS Command Injection in Dokploy before 0.29.13 - CVE-2026-72869 Aug 10, 2026

AnalysisAI

OS command injection in Dokploy (self-hosted PaaS) before 0.29.13 lets an authenticated user with the backup:restore permission run arbitrary commands on the Docker-privileged host. The backup.restoreBackupWithLogs tRPC subscription forwards an attacker-controlled databaseName into shell strings that Node.js exec passes to /bin/sh before docker exec, so the outer host shell expands injected metacharacters. Rated CVSS 9.9 with a scope change to the host; no public exploit identified at time of analysis, though the upstream fix PR ships regression tests containing working injection payloads.

Technical ContextAI

Dokploy is a free, self-hostable Platform-as-a-Service (a Heroku/Vercel-style deployment layer) that orchestrates application and database containers via Docker. The vulnerable code in packages/server/src/utils/restore/utils.ts (and the parallel backups/utils.ts) builds restore/backup commands for PostgreSQL, MariaDB, MySQL, and MongoDB by string-interpolating user-supplied values (databaseName, user, password) directly into a docker exec ... bash -c "..." template. That template is handed to Node.js child_process exec, which spawns /bin/sh -c on the host; the host shell expands $(), backticks, and quote-breakouts in databaseName before docker even runs. This is a classic CWE-77 (Improper Neutralization of Special Elements used in a Command) issue caused by unescaped interpolation across two shell layers. The fix moves all user values into docker exec -e VAR=<shell-quote-escaped> environment variables referenced as "$VAR" inside a single-quoted inner script, so the values never appear inline in shell text.

RemediationAI

Vendor-released patch: upgrade to Dokploy 0.29.13, which rewrites the backup and restore command builders to pass database name, user, and password as shell-quote-escaped docker exec -e environment variables consumed inside a single-quoted inner script (see PR https://github.com/Dokploy/dokploy/pull/4862 and commit ccd2e83c57d99f725220d37e0152270e0827d71b). Upgrading is the only complete fix. If you cannot patch immediately, restrict the blast radius by removing the backup:restore permission from all but fully trusted operators and auditing which accounts currently hold it, and treat the Dokploy control plane as host-root-equivalent by placing its web interface behind a VPN or IP allowlist so account compromise is harder - the trade-off is that legitimate restore operations become manual/gated and remote administrative access is reduced. Do not rely on input validation of database names as a substitute for the upgrade, since crafting a robust denylist across four DB engines and two shell layers is error-prone. Advisory: https://github.com/Dokploy/dokploy/security/advisories/GHSA-f7mp-9jfp-mjrr.