Quick answers
- Is CVE-2026-93425 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93425 being exploited in the wild.
- How severe is CVE-2026-93425?
- Critical severity, with a CVSS score of 9.9, published 24 September 2026.
- Which products and versions are affected?
- Dokploy before 0.29.13.
- Is there a fix for CVE-2026-93425?
- A patch was published on 2026-07-20. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-93425 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-93425?
- 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 patch.readRepoDirectories tRPC procedure passes user-controlled repoPath directly into a shell command via child_process.exec without argument quoting, allowing shell metacharacter injection. An authenticated user with service:read permission can exploit this to execute arbitrary commands as root; because /var/run/docker.sock is typically mounted, attackers gain Docker control. The vulnerability was fixed in version 0.29.13 by applying shell-quote escaping to user-controlled paths.
Affected products
- Dokploy Dokploy before 0.29.13
Timeline
- 2026-09-24: disclosed
- 2026-07-20: patched