Quick answers
- Is CVE-2026-72733 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72733 being exploited in the wild.
- How severe is CVE-2026-72733?
- Critical severity, with a CVSS score of 9.9, published 10 August 2026.
- Which products and versions are affected?
- Dokploy before 0.29.13.
- Is there a fix for CVE-2026-72733?
- A patch was published on 2026-07-19: Fixed in version 0.29.13 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-72733 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-72733?
- Check whether you run Dokploy at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is an OS command injection vulnerability (CWE-78) in the backup.restoreBackupWithLogs tRPC subscription. The vulnerability exists in multiple database restore utilities (postgres.ts, mysql, mariadb, mongo, libsql) where user-controlled databaseName and backupFile parameters are interpolated directly into shell commands without proper escaping. The commands are executed via execAsync or execAsyncRemote, which pass them to a shell running in the Dokploy host context. The attack vector is network-based through the tRPC subscription endpoint, requiring authentication with backup-restore permission. An attacker can achieve remote code execution even when no valid database container or backup file exists. The vulnerability was patched in version 0.29.13 by passing database identifiers via environment variables instead of shell interpolation.
Affected products
- Dokploy Dokploy before 0.29.13
Timeline
- 2026-08-10: disclosed
- 2026-07-19: patched: Fixed in version 0.29.13