Quick answers
- Is CVE-2026-72738 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72738 being exploited in the wild.
- How severe is CVE-2026-72738?
- 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-72738?
- A patch was published on 2026-07-20: Security fix committed (v0.29.13 released 2026-07-21) Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-72738 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-72738?
- 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 in the backup.listBackupFiles tRPC endpoint (apps/dokploy/server/api/routers/backup.ts). The search parameter is passed through normalizeS3Path and directly interpolated into an rclone lsjson command executed via child_process.exec() without proper escaping. An authenticated attacker with backup:read permission can inject shell metacharacters (such as $(), backticks, quotes) to break out of the rclone command context and execute arbitrary commands. The fix in version 0.29.13 wraps all S3 credential flags, search paths, and backup file paths with shell-quote's quote() function to prevent command injection.
Affected products
- Dokploy Dokploy before 0.29.13
Timeline
- 2026-08-10: disclosed: CVE-2026-72738 published
- 2026-07-20: patched: Security fix committed (v0.29.13 released 2026-07-21)