Quick answers
- Is CVE-2026-72736 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-72736 being exploited in the wild.
- How severe is CVE-2026-72736?
- Critical severity, with a CVSS score of 9.9, published 10 August 2026.
- Which products and versions are affected?
- Dokploy prior to 0.29.13.
- Is there a fix for CVE-2026-72736?
- A patch was published on 2026-07-19: Fix released in version 0.29.13 on July 21, 2026 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-72736 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-72736?
- 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
The vulnerability is an OS command injection flaw (CWE-78) in Dokploy's registry credential testing and Docker Swarm cluster management endpoints. User-controlled values (nodeId, registryTag, imageName) are interpolated directly into shell commands via unquoted template literals and passed to remote execution via SSH (execAsyncRemote), bypassing the safer local execution paths (execFileAsync or Docker API). The vulnerable endpoints include cluster.removeWorker, swarm image upload (getRegistryCommands), and registry testing functionality. An authenticated attacker can inject shell metacharacters and arbitrary commands that execute with the privileges of the Dokploy process. The vulnerability is fixed in version 0.29.13 by applying shell-quoting to all user-controlled values before command interpolation.
Affected products
- Dokploy Dokploy prior to 0.29.13
Timeline
- 2026-08-10: disclosed
- 2026-07-19: patched: Fix released in version 0.29.13 on July 21, 2026