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.
CVE-2026-72733
This critical-severity CVE scores 9.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 9.9
- EG Score
- 9.9(medium)
- EG Risk
- 61(Track*)EG Risk 61/100SSVC: Track*
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity99% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Watch closely — could escalate to Attend. - EPSS PROB
- 0%
- EPSS %ILE
- 40%
- KEV
- Not listed
Published
August 10, 2026
Last Modified
August 10, 2026
Advisory Details (6)
Auto-updated Aug 24, 2026OS Command Injection via `databaseName` / `backupFile` in database restore · Advisory · Dokploy/dokploy · GitHub
https://github.com/Dokploy/dokploy/security/advisories/GHSA-2xjq-p4xx-5x2pv0.29.13
Patch available: Dokploy/dokploy v0.29.13
https://github.com/Dokploy/dokploy/releases/tag/v0.29.13fix(security): OS command injection in database backup/restore commands
Patch available: Dokploy/dokploy v0.29.13 (PR #4862 merged 2026-07-20)
https://github.com/Dokploy/dokploy/pull/4862commit eeb6e7b8ea88 (Dokploy/dokploy)
Patch available: Dokploy/dokploy v0.29.13 (contains commit eeb6e7b8ea88)
https://github.com/Dokploy/dokploy/commit/eeb6e7b8ea88e4b4b1fac8460755464100516ac9commit ccd2e83c57d9 (Dokploy/dokploy)
Patch available: Dokploy/dokploy v0.29.13 (contains commit ccd2e83c57d9)
https://github.com/Dokploy/dokploy/commit/ccd2e83c57d99f725220d37e0152270e0827d71bcommit 8539a5c82f47 (Dokploy/dokploy)
Patch available: Dokploy/dokploy v0.29.13 (contains commit 8539a5c82f47)
https://github.com/Dokploy/dokploy/commit/8539a5c82f47eb3fd1464b574eb034c6dc2a6bbdWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 42× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-30 04:37 UTCEG score recompute
- 2026-08-30 01:22 UTCEPSS rescore
- 2026-08-29 09:56 UTCEG score recompute
- 2026-08-28 21:42 UTCEPSS rescore
- 2026-08-27 15:12 UTCEG score recompute
- 2026-08-27 14:25 UTCEPSS rescore
- 2026-08-26 18:54 UTCEG score recompute
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-25 13:59 UTCEG score recompute
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-24 14:50 UTCEG score recompute
- 2026-08-24 10:58 UTCEG score recompute
- 2026-08-23 04:07 UTCEG score recompute
- 2026-08-23 00:19 UTCEPSS rescore
- 2026-08-22 01:08 UTCEG score recompute
- 2026-08-21 23:49 UTCEPSS rescore
- 2026-08-21 01:58 UTCEG score recompute
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 18:44 UTCEG score recompute
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-18 15:18 UTCEG score recompute
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 15:39 UTCEG score recompute
- 2026-08-17 13:47 UTCEPSS rescore
Show 17 moreShow fewer
- 2026-08-16 16:31 UTCEG score recompute
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 04:58 UTCEG score recompute
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 01:58 UTCEG score recompute
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-13 22:59 UTCEG score recompute
- 2026-08-13 22:00 UTCEPSS rescore
- 2026-08-12 16:06 UTCEG score recompute
- 2026-08-12 13:51 UTCEPSS rescore
- 2026-08-11 16:47 UTCEG score recompute
- 2026-08-10 21:32 UTCEG score recompute
- 2026-08-10 21:15 UTCEG score recompute
- 2026-08-10 18:24 UTCEG score recompute
- 2026-08-10 17:35 UTCEG score recompute
- 2026-08-10 17:35 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-78
- CVE-2009-20011EG 10.0CRITICAL
- CVE-2011-10017EG 10.0CRITICAL
- CVE-2012-1166EG 10.0EPSS p91HIGH
- CVE-2012-2976EG 10.0EPSS p92HIGH
- CVE-2012-2953EG 10.0EPSS p99HIGH
- CVE-2011-4502EG 10.0EPSS p92HIGH
- CVE-2011-2148EG 10.0EPSS p92HIGH
- CVE-2011-0382EG 10.0EPSS p90HIGH
- CVE-2011-0381EG 10.0EPSS p92HIGH
- CVE-2011-0372EG 10.0HIGH
Frequently asked(5)
What is CVE-2026-72733?
When was CVE-2026-72733 disclosed?
Is CVE-2026-72733 actively exploited?
What is the CVSS score of CVE-2026-72733?
How do I remediate CVE-2026-72733?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-72733
Is Your Infrastructure Affected by CVE-2026-72733?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.