Quick answers
- Is CVE-2026-45629 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-45629 being exploited in the wild.
- How severe is CVE-2026-45629?
- Critical severity, with a CVSS score of 9.9, published 29 May 2026.
- Which products and versions are affected?
- Dokploy <= 0.28.8.
- Is there a fix for CVE-2026-45629?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-45629 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-45629?
- 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
An OS command injection vulnerability exists in the `/listen-deployment` WebSocket endpoint within `apps/dokploy/server/wss/listen-deployment.ts`. The endpoint accepts a `logPath` parameter which is validated using `readValidDirectory()`; however, this function uses `path.resolve()`, which does not neutralize shell metacharacters. The validated path is then directly interpolated into a shell command (`tail -n +1 -f ${logPath}`) and executed via SSH on remote servers. Furthermore, the endpoint bypasses standard tRPC permission middleware, requiring only basic authentication and organization membership rather than specific server permissions. An attacker can use characters like `;` to append and execute arbitrary commands with the privileges of the SSH user.
Affected products
- Dokploy Dokploy <= 0.28.8
Timeline
- 2026-05-11: advisory: Original GitHub security advisory published
- 2026-05-29: disclosed: CVE published to NVD