What is the CVSS score of EUVD-2026-55679?

EUVD-2026-55679 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.5%.

Which versions of Dokploy are affected by EUVD-2026-55679?

Dokploy self-hosted PaaS deployments running versions before 0.29.13 are vulnerable to privilege escalation through the backup-restore feature, allowing authenticated backup operators to execute…. A patch is available.

How to fix or mitigate EUVD-2026-55679?

Within 24 hours, audit all Dokploy deployments to identify installations running versions prior to 0.29.13 and review access logs for backup-restore permission usage to detect suspicious activity. Immediately restrict the backup-restore permission to essential personnel only and require manual approval for all backup restoration operations. Within 7 days, establish a patching schedule with your infrastructure and security teams, monitor Dokploy's official security advisories for patch availability, and configure off-host backup storage to limit compromise scope to backup data rather than the entire host system. Within 30 days, complete upgrade testing in non-production environments and deploy patches to all affected Dokploy instances, then re-enable full permissions with enhanced audit logging.

Dokploy EUVD-2026-55679

| CVE-2026-72733 CRITICAL

OS Command Injection (CWE-78)

2026-08-10 GitHub_M

PostgreSQL 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

Network tRPC reach and simple metacharacter payloads give AV:N/AC:L; the backup-restore role gives PR:L; command execution escapes the app to the host so S:C with full C:H/I:H/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 - 18:19 EUVD

Source Code Evidence Fetched

Aug 10, 2026 - 18:06 vuln.today

Analysis Generated

Aug 10, 2026 - 18:06 vuln.today

CVE Published

Aug 10, 2026 - 17:26 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 builds database restore shell pipelines from the user-controlled databaseName and backupFile fields without safely separating them from shell syntax. packages/server/src/utils/restore/utils.ts interpolates databaseName into database-specific restore commands, while packages/server/src/utils/restore/postgres.ts and the analogous restore modules interpolate backupFile into rclone paths. An authenticated member with backup-restore permission can inject operating-system commands that execute in the Dokploy host context through execAsync or execAsyncRemote, even when no valid database container or backup file exists. 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-72733 Aug 10, 2026

AnalysisAI

OS command injection in Dokploy (self-hostable PaaS) before 0.29.13 lets an authenticated user holding the backup-restore permission run arbitrary shell commands on the underlying Dokploy host. The backup.restoreBackupWithLogs tRPC subscription concatenates the user-supplied databaseName and backupFile fields directly into database restore and rclone shell pipelines, so crafted values break out of the intended command and execute via execAsync/execAsyncRemote. There is no public exploit identified at time of analysis and it is not on CISA KEV, but the fixing pull request (#4862) ships a regression test enumerating working injection payloads, and the CVSS of 9.9 with scope change reflects full host takeover from a low-privileged application role.

Technical ContextAI

Dokploy is a Node.js/TypeScript Vercel-and-Heroku-style platform that orchestrates Docker containers on a host and exposes its API over tRPC. The flaw is a classic CWE-78 OS Command Injection: packages/server/src/utils/restore/utils.ts interpolates the databaseName into database-specific restore commands (Postgres, MySQL, MariaDB, MongoDB), and packages/server/src/utils/restore/postgres.ts plus sibling modules interpolate backupFile into rclone paths. These strings are assembled into docker exec ... bash -c "..." pipelines and executed through execAsync (local) or execAsyncRemote (SSH to a remote node). Because the fields are placed inside double-quoted or single-quoted shell context without escaping, shell metacharacters ($(...), backticks, quotes, semicolons) terminate the intended command. The upstream fix moves user values out of the inline command text into docker exec -e VAR=<shell-quote escaped> environment variables referenced as "$VAR" inside a single-quoted inner script, neutralizing both the outer and inner shell layers.

RemediationAI

Vendor-released patch: upgrade Dokploy to 0.29.13, which is the fixed release (https://github.com/Dokploy/dokploy/releases/tag/v0.29.13); the corresponding changes are in pull request #4862 and commits 8539a5c, ccd2e83 and eeb6e7b. The fix passes databaseName/backupFile as shell-quoted docker exec -e environment variables instead of inlining them, so upgrading is the primary and complete remediation. If you cannot upgrade immediately, restrict who holds the backup-restore permission to a minimal set of fully trusted administrators (removing it from all non-essential members closes the low-privilege attack path), avoid exposing the Dokploy control plane to untrusted networks, and audit restore activity - the trade-off is that revoking backup-restore blocks legitimate self-service restores until the patch is applied. Refer to advisory GHSA-2xjq-p4xx-5x2p for authoritative guidance.